DoraCMS

DoraCMS 是一个基于 EggJS 3.x + Vue 3 + TypeScript 的现代化内容管理系统,采用 pnpm monorepo 架构管理。它不仅仅是一个 CMS 系统,更是一个优秀的企业级应用架构实践。

Runs with mockssource: GitHubhomepageJavaScriptMITcommit bdaded858ce6

JavaScript, MIT licensed. The project labels itself: cms, doracms, eggjs, element ui, mit license, mongodb, nodejs and nodejscms.

DoraCMS runs, with stand-ins for the services it depends on. An Argusic agent installed it in 1.5 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

pnpm install succeeds. 75 server-side tests pass with mongodb-memory-server (68 pure unit + 7 webhook integration). Server cannot start standalone without Redis. Egg-watcher plugin patched to add none event source. Two test fixtures repaired.

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

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.24 (measured)
recorded runs
2
last tested
stars
3,553
forks
1,033
open issues
26
watchers
179
size
52 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 DoraCMS, 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.

  • Egg-watcher package missing "none" event source - tests using config.watcher = {type: "none"} crashed with EventSource is not a constructor5 minutes
  • Missing test fixtures for framework test (service + favicon)2 minutes
  • Missing test/mock_data.js - content-publish-ai.test.js could not load1 minute
  • Server cannot start without Redis - Bull queue crashes on startup
Install time
2 minutes
Cold machine to finish
26 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
75 tests passing: 68 pure unit + 7 webhook integration with mongodb-memory-server, 0 failures
Model tokens used
835,052
Exact commit tested
bdaded858ce6
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
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

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

**Fixes applied**:
1. Created `server/test/mock_data.js` - missing dependency for `content-publish-ai.test.js`
2. Created `server/test/fixtures/example/app/service/test.js` - missing fixture for framework test
3. Created `server/test/fixtures/example/app/public/favicon.ico` - missing fixture for framework te…
4. Patched `egg-watcher` plugin to add a `none` event source type (allows `config.watcher = { type:…
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 1…
 succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 1.5, "errors": [{"msg": "E…
2026-11-09T13:57:25.852416Z ERROR codex_core::session: failed to record rollout items: thread 01a1c…
tokens used
835,052

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

  • Installed in 1.5 minutes, faster than the median of the 28 comparable projects Argusic has measured.
  • Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
  • 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

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.

Of the 29 cms projects Argusic has installed and timed, DoraCMS was the 5th fastest to reach a running state, and 25 of 29 reached one at all.

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/3Runs with mocks92.000.24
Argusic Runner1/3Runs with mocks92.000.26

Topics (from GitHub)

cmsdoracmseggjselement-uimit-licensemongodbnodejsnodejscmspnpmqiankuntypescriptvuevuejs

Embed the badge

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

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

Questions

Does DoraCMS run?
DoraCMS runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 2 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test DoraCMS?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit bdaded858ce6. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test DoraCMS?
The run that produced this verdict cost $0.24: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does DoraCMS take to install?
1.5 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 DoraCMS need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing DoraCMS?
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 DoraCMS compare with the alternatives?
Of the 29 cms projects Argusic has installed and timed, DoraCMS was the 5th fastest to reach a running state, and 25 of 29 reached one at all.
Where is the evidence for DoraCMS?
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