typicms

A modular multilingual CMS built with Laravel, enabling developers to manage structured content like pages, news, events, and more.

Runssource: GitHubPHPMITcommit d12777b241fe

PHP, MIT licensed. The project labels itself: cms, laravel, multilingual, php and website builder.

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

TypiCMS Laravel app installed with SQLite database, migrations and seeders run, artisan serve responds on port 8000 with health endpoint at /up returning 200

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 60 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
60 / 100
cost of the verifying run
$0.15 (measured)
recorded runs
2
last tested
stars
1,619
forks
483
open issues
4
watchers
70
size
25 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 typicms, 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 or Composer available in container3 minutes
  • Missing canonicalUrl() helper function in app/helpers.php2 minutes
  • No MySQL/PostgreSQL available1 minute
  • No Redis available for session/cache1 minute
  • 28 vendor unit tests fail due to Pest/Laravel integration configuration for vendor directories
Install time
20 minutes
Cold machine to finish
24 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
php artisan serve started, curl http://localhost:8000/up returned 200, curl http://localhost:8000/ returned 404 (expected), php vendor/bin/pest --testsuite=Unit ran 68 assertions with 40 passing
Model tokens used
436,976
Exact commit tested
d12777b241fe
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.

The app is running successfully. Let me summarize the final state:
- `/up` (Laravel health check): **200** ✓
- `/` returns **404** as expected (the CMS requires a locale prefix like `/en`)
- Database: 24 tables created and seeded ✓
- Stack: PHP 8.5 (static binary), SQLite, Laravel 13, Composer 2.8 ✓
tokens used
436,976
The app is running successfully. Let me summarize the final state:
- `/up` (Laravel health check): **200** ✓
- `/` returns **404** as expected (the CMS requires a locale prefix like `/en`)
- Database: 24 tables created and seeded ✓
- Stack: PHP 8.5 (static binary), SQLite, Laravel 13, Composer 2.8 ✓

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 5 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 20 minutes to install, slower than the median of the 28 comparable projects Argusic has measured.

Of the 29 cms projects Argusic has installed and timed, typicms was the 23rd fastest to reach a running state, and 25 of 29 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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Did not run20.000.00
Argusic Runner1/3Runs100.000.15

Topics (from GitHub)

cmslaravelmultilingualphpwebsite-builder

Embed the badge

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

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

Questions

Does typicms run?
Yes. typicms runs. Argusic installed and launched it on a clean machine in 20 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test typicms?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit d12777b241fe. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test typicms?
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 typicms take to install?
20 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 typicms need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing typicms?
5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does typicms compare with the alternatives?
Of the 29 cms projects Argusic has installed and timed, typicms was the 23rd fastest to reach a running state, and 25 of 29 reached one at all.
Where is the evidence for typicms?
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