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 58 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Kanboard installs via composer, its 1207-test SQLite unit suite passes, the CLI runs, and the web app serves /healthcheck.php 200 and authenticates admin/admin to a rendered dashboard over HTTP.
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
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.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- PHPUnit error: Call to undefined function Kanboard\Group\ldap_escape() (ext-ldap missing)45 minutes
- Attempted stock static PHP builds lack ext-ldap; building custom static PHP blocked by GitHub API 403 rate limit and missing build deps (bison/re2c/flex/autoconf/automake/libtool not present, no root)26 minutes
- No PHP runtime in container (php: not found)8 minutes
- composer.phar would not run: /usr/bin/env: 'php': No such file or directory1 minute
- Install time
- 58 minutes
- Cold machine to finish
- 60 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- ./vendor/bin/phpunit -c tests/units.sqlite.xml exited 0 with Tests: 1207, Assertions: 180768, Errors: 0, Failures: 0; php -S + curl: /healthcheck.php 200, login POST admin/admin 302 to dashboard, dashboard GET 200 with title 'Dashboard for admin'; ./cli version printed main.unknown_revision
- Model tokens used
- 5,338,066
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- The only source-code change is `app/functions.php`; `vendor/` + `vendor/bin/` and `config.php` ar… tokens used 5,338,066 All verified. Here is the final report. **Work Done** - Standard install: downloaded a static PHP 8.4.27 CLI (the container has no PHP; no system install… - Ran `./vendor/bin/phpunit -c tests/units.sqlite.xml`: first run failed with 1 error — `Call to un… - Fix: added a `ldap_escape()`/`LDAP_ESCAPE_*` compatibility shim to `app/functions.php` (guarded b… - Launch: `php -S 127.0.0.1:8929`; `/healthcheck.php` → 200; real login flow `admin/admin` (with CS… **Notes** - I also spent time attempting a full static PHP build with `ext-ldap`; the distro's GitHub API rat… - The only source-code change is `app/functions.php`; `vendor/` + `vendor/bin/` and `config.php` ar…
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.
- 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 MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 58 minutes to install, slower than the median of the 4 comparable projects Argusic has measured.
Of the 5 agile projects Argusic has installed and timed, kanboard was the 5th fastest to reach a running state, and 4 of 5 reached one at all.
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
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/kanboard)Questions
- Does kanboard run?
- Yes. kanboard runs. Argusic installed and launched it on a clean machine in 58 minutes, hitting 4 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. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test kanboard?
- The run that produced this verdict cost $1.08: 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?
- 58 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?
- 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.
- How does kanboard compare with the alternatives?
- Of the 5 agile projects Argusic has installed and timed, kanboard was the 5th fastest to reach a running state, and 4 of 5 reached one at all.
- Where is the evidence for kanboard?
- 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.