deco

Git-based Visual CMS for Deno, </> htmx and Tailwind apps. Deploy on any Deno-compatible host.

Runssource: GitHubhomepageTypeScriptApache-2.0commit 7dbb79ae2573

TypeScript, Apache-2.0 licensed. The project labels itself: cms, deno, fresh, frontend, hacktoberfest, htmx, platform and preact.

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

Deno 2.9.8 installed, all 82 tests pass across 14 test files, the deco engine daemon starts and serves HTTP on APP_PORT, type-checking passes, and benchmarks run without errors.

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

verdict
Runs
Argusic Score
96 / 100
cost of the verifying run
$0.02 (measured)
recorded runs
2
last tested
stars
849
forks
54
open issues
79
watchers
6
size
6 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 deco, 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.

  • Deno binary not found in PATH1 minute
  • Daemon fails on default port 8000 (EADDRINUSE)0.5 minutes
Install time
6 minutes
Cold machine to finish
6 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
deno test --unstable-http -A . returned 82 passed, 0 failed; daemon launched with APP_PORT=8765 DECO_SITE_NAME=test and responded with 404 on / (expected for engine without a site project), plus health probes all passed
Model tokens used
77,550
Exact commit tested
7dbb79ae2573
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 "Started at 19:16"; echo "Now at $(date +%M)"; echo "Elapsed ~5 minutes"' in /wor…
 succeeded in 0ms:
Started at 19:16
Now at 22
Elapsed ~5 minutes
Here's my final report:
2026-11-21T19:22:08.816112Z ERROR codex_core::session: failed to record rollout items: thread 01a1f…
2026-11-21T19:22:08.816178Z ERROR codex_core::session: failed to record rollout items: thread 01a1f…
tokens used
77,550
Here's my 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 6 minutes, faster than the median of the 29 comparable projects Argusic has measured.
  • 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 Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

Of the 30 cms projects Argusic has installed and timed, deco was the 12th 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.
  • A quick evaluation: it was running 6 minutes after the clone.

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/3Runs100.000.02
Argusic Runner1/3Runs with mocks92.000.29

Topics (from GitHub)

cmsdenofreshfrontendhacktoberfesthtmxplatformpreacttailwindtailwindcsstypescriptwebflowwordpress

Embed the badge

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

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

Questions

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