kanboard

Kanban project management software

Runssource: GitHubhomepagePHPMITcommit cf53b54597b6

PHP, MIT licensed. The project labels itself: agile, kanban, kanboard, project management and self hosted.

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

Kanboard runs on FrankenPHP 8.4.3 with SQLite, passing 1207 unit tests and serving the login page and healthcheck endpoint.

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.05 (measured)
recorded runs
1
last tested
stars
9,884
forks
1,993
open issues
170
watchers
308
size
75 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 kanboard, 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.

  • No PHP binary in container3 minutes
  • No composer1 minute
  • No config.php1 minute
Install time
13 minutes
Cold machine to finish
12 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
phpunit -c tests/units.sqlite.xml: 1207 tests, 180942 assertions, 1 warning, OK; curl /healthcheck.php returned 200; curl login page returned 200 with Kanboard HTML
Model tokens used
258,983
Exact commit tested
cf53b54597b6
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.

 succeeded in 0ms:
Start: check README
End: Sun Sep 27 13:28:03 UTC 2026
exec
/bin/sh -lc "ARGUSIC_RESULT:{\"install_succeeded\":true,\"launch_succeeded\":true,\"install_minutes…
 exited 127 in 0ms:
/bin/sh: 1: ARGUSIC_RESULT:{install_succeeded:true,launch_succeeded:true,install_minutes:13,errors:…
exec
/bin/sh -lc "echo 'ARGUSIC_RESULT:{\"install_succeeded\":true,\"launch_succeeded\":true,\"install_m…
 succeeded in 0ms:
tokens used
258,983

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 13 minutes.
  • Recovered from all 3 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 MIT, as reported by its host.

What did not, or is not known

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

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.

  • onedev verified to run · Java · 2 shared topics

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.05

Topics (from GitHub)

agilekanbankanboardproject-managementself-hosted

Embed the badge

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

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

Questions

Does kanboard run?
Yes. kanboard runs. Argusic installed and launched it on a clean machine in 13 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test kanboard?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit cf53b54597b6. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test kanboard?
The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does kanboard take to install?
13 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 kanboard need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing kanboard?
3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for kanboard?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion