concretecms
Official repository for Concrete CMS development
Runssource: GitHubhomepagePHPMITcommit bf2747aab53b
PHP, MIT licensed. The project labels itself: cms, concrete5, concretecms, content management system, framework and php.
concretecms runs. An Argusic agent installed it in 32.4 minutes and hit 8 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Concrete CMS dependencies are installed via composer and 3180 PHPUnit tests pass (10 skipped, 9 incomplete) against a locally-stood-up MariaDB 10.11 database on port 3307, running on static PHP 8.3.32
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 96 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.
- No MySQL/MariaDB server available15 minutes
- Composer install blocked by security advisories (PKSA-*) and platform.php=7.3 version mismatch for twig/twig3 minutes
- MariaDB listening on port 3307 but test config expected default 3306 with a socket2 minutes
- PHP and Composer not installed in container1.5 minutes
- ext-intl missing from common PHP static build, blocking laminas/laminas-i18n dependency1.5 minutes
- DatabaseTest::testValidConnection didn't pass port to createConnection(), causing connection refused1 minute
- Install time
- 32 minutes
- Cold machine to finish
- 33 minutes
- Errors hit and fixed
- 8 hit, 8 fixed with no human help
- How the result was proved
- phpunit ran 3180 tests with 10102 assertions, exit code 0, 'OK, but incomplete, skipped, or risky tests!' with 10 skipped and 9 incomplete
- Model tokens used
- 502,100
- Exact commit tested
- bf2747aab53b
- 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.
|-------|-----| | PHP not installed | Downloaded static PHP 8.3.32 (bulk build with all extensions) | | ext-intl missing | Common build lacked it; switched to bulk build | | Composer security advisory block | Fixed malformed `audit.ignore` list, set `audit.block=false` | | PHP 7.3 platform mismatch for Twig | Set `config.platform.php=8.3.32` (later reverted to 7.3 for … | No MySQL server | Downloaded MariaDB 10.11 Ubuntu packages, extracted binaries, initialized + sta… | Test config had wrong port | Added `'port' => '3307'` to `tests/config/database.php` | | `DatabaseTest::testValidConnection` missing port | Added `'port'` param to `createConnection()` | | `MinPHPVersionTest` expected platform 7.3 | Reverted `config.platform.php` to `7.3` | | `ExecutableFilesTest` found stray artifact | Removed `run_tests.py` | ## Final result **10 tests skipped** (Redis, HTTP client, msgfmt, etc.) and **9 incomplete** (not yet implemented) …
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 8 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 32.4 minutes to install, slower than the median of the 29 comparable projects Argusic has measured.
Of the 30 cms projects Argusic has installed and timed, concretecms was the 28th fastest to reach a running state, and 27 of 30 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
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.15 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.09 |
Topics (from GitHub)
cmsconcrete5concretecmscontent-management-systemframeworkphp
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/concretecms)Questions
- Does concretecms run?
- Yes. concretecms runs. Argusic installed and launched it on a clean machine in 32 minutes, hitting 8 errors on the way, and recorded the session.
- How did Argusic test concretecms?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit bf2747aab53b. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test concretecms?
- The run that produced this verdict cost $0.15: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does concretecms take to install?
- 32.4 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 concretecms need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing concretecms?
- 8 things broke in the recorded run, and 8 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does concretecms compare with the alternatives?
- Of the 30 cms projects Argusic has installed and timed, concretecms was the 28th fastest to reach a running state, and 27 of 30 reached one at all.
- Where is the evidence for concretecms?
- 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.