decap-cms
A Git-based CMS for Static Site Generators
Runssource: GitHubhomepageJavaScriptMITcommit 1d5868347d3d
JavaScript, MIT licensed. The project labels itself: cms, content management system, decap cms, git based cms, headless cms, jamstack, javascript and netlify cms.
decap-cms runs. An Argusic agent installed it in 25 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
pnpm install completes with no errors; all 119 test suites pass (1495/2799 tests, 1304 skipped as expected); decap-cms-core builds both ESM (126 files) and production UMD (1.26 MiB) bundles successfully; decap-cms-lib-util ESM build (20 files) succeeds.
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.
- [email protected] overridden in pnpm-workspace.yaml but is ESM-only; [email protected] (Cypress dep) uses require('clean-stack'), causing ERR_REQUIRE_ESM in Cypress postinstall5 minutes
- pnpm not found in PATH; npm install -g failed due to /usr/local permissions3 minutes
- Install time
- 25 minutes
- Cold machine to finish
- 18 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- pnpm run test:unit (jest --no-cache --runInBand) completed: 119 passed, 2 skipped, 1495 tests passed, 1304 skipped, 138 snapshots passed in 89s. pnpm run --filter decap-cms-core build:esm compiled 126 files. pnpm run --filter decap-cms-core build produced 1.26 MiB webpack bundle. pnpm run --filter decap-cms-lib-util build:esm compiled 20 files.
- Model tokens used
- 265,511
- Exact commit tested
- 1d5868347d3d
- 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.
exec /bin/sh -lc 'echo "=== Time tracking ===" && date -u +%s' in /work/repo succeeded in 0ms: === Time tracking === 1790386933 exec /bin/sh -lc 'cd /work/repo && grep -r "clean-stack" pnpm-workspace.yaml package.json --include="" 2… exited 1 in 0ms: Now I have all the data. Let me assemble the final report. tokens used 265,511 Now I have all the data. Let me assemble the final report.
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 25 minutes.
- Recovered from all 2 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.
Run history
Topics (from GitHub)
cmscontent-management-systemdecap-cmsgit-based-cmsheadless-cmsjamstackjavascriptnetlify-cmsnpm-packagereactstaticstatic-sitestatic-site-generator
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/decap-cms)Questions
- Does decap-cms run?
- Yes. decap-cms runs. Argusic installed and launched it on a clean machine in 25 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test decap-cms?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1d5868347d3d. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test decap-cms?
- The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does decap-cms take to install?
- 25 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 decap-cms need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing decap-cms?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for decap-cms?
- 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.