diboot

写的更少, 性能更好 -> 为开发人员打造的低代码开发框架,基础框架可免写90%的SQL,同时具备极强的零代码模型表单页面流程的设计能力和代码生成能力,可在pro-code、low-code、no-code之间自由选择灵活切换,全方位赋能开发。

Runssource: GitHubhomepageJavaApache-2.0commit cd211a2dcc06

Java, Apache-2.0 licensed. The project labels itself: flowable, low code, low code framework, mybatis, mybatis plus, spring, spring boot and spring cloud.

diboot runs. An Argusic agent installed it in 12 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

All 9 Diboot modules compile, package, and install. Example REST API compiles. Test suite connects to real MariaDB and executes 6 integration tests with 2 passing and 4 failing on seed data assertion checks (not infrastructure).

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.32 (measured)
recorded runs
2
last tested
stars
1,611
forks
287
open issues
0
watchers
51
size
53 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing diboot, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Tests require MySQL on port 33075 minutes
  • Java and Maven not pre-installed2 minutes
  • JUnit4 tests not detected by Surefire (only JUnit Platform provider)2 minutes
  • rest-api-example failed to compile: FileAccessInterceptor not found1 minute
Install time
12 minutes
Cold machine to finish
45 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
mvn test -pl diboot-core-starter -am ran 6 tests (2 passed, 4 failed due to empty seed data queries), all 9 modules plus rest-api-example compiled to classes
Model tokens used
278,190
Exact commit tested
cd211a2dcc06
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

2. `FileAccessInterceptor` compilation error in rest-api-example → Fixed by running `mvn install` o…
3. JUnit 4 tests not detected by Surefire → Fixed by adding `junit-vintage-engine` dependency.
4. MariaDB required for tests → Fixed by downloading and starting MariaDB 10.11.8 in-memory.
exec
/bin/sh -lc "echo 'ARGUSIC_RESULT: {\"install_succeeded\": true, \"launch_succeeded\": true, \"inst…
 succeeded in 0ms:
Let me verify there are no leftover processes.
2026-11-14T11:23:16.426407Z ERROR codex_core::tools::router: error=exec_command failed: CreateProce…
The ARGUSIC_RESULT line was printed above. The result is complete.
tokens used
278,190
The ARGUSIC_RESULT line was printed above. The result is complete.

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 12 minutes.
  • Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.32
Argusic Runner1/3Runs100.000.19

Topics (from GitHub)

flowablelow-codelow-code-frameworkmybatismybatis-plusspringspring-bootspring-cloudspringbootvue

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/diboot.svg)](https://argusic.com/subject/diboot)

Questions

Does diboot run?
Yes. diboot runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test diboot?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit cd211a2dcc06. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test diboot?
The run that produced this verdict cost $0.32: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does diboot take to install?
12 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does diboot need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing diboot?
4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for diboot?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion