hexo
A fast, simple & powerful blog framework, powered by Node.js.
Runssource: GitHubhomepageTypeScriptMITcommit 751e856691bf
TypeScript, MIT licensed. The project labels itself: hacktoberfest, hexo, javascript, nodejs, static site generator and typescript.
hexo runs. An Argusic agent installed it in 33 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Hexo 8.1.2 installs, builds, passes its full test suite (1292 passing, 0 failing), and a generated blog served by hexo server answered HTTP 200 on the homepage and a post page.
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.
- 4 tests in test/scripts/processors/asset.ts failed (ANSI color assertion, cuid id mismatch, delete tests) on first run12 minutes
- Node 18.19.1 in container is below engines (node >=20.19.0); npm test crashed with ERR_UNKNOWN_FILE_EXTENSION on .ts and ERR_REQUIRE_ESM on tildify/nanoid10 minutes
- hexo server process exited when its exec session ended (no listener on port)3 minutes
- Install time
- 33 minutes
- Cold machine to finish
- 35 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- npm test with Node 20.19.1 and FORCE_COLOR=1 NO_COLOR= exited 0 with 1292 passing / 5 pending / 0 failing; curl http://127.0.0.1:4323/ and /2026/11/01/hello-world/ both returned 200
- Model tokens used
- 390,976
- Exact commit tested
- 751e856691bf
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
tokens used
390,976
All verification is complete. Final summary and result line follow.
## What I did
- Repo: Hexo 8.1.2 (`package.json` declares `node >=20.19.0`; container had Node 18.19.1).
- Standard install (`npm ci`): 692 packages installed cleanly, `npm run build` (tsc) succeeded, `np…
- Fixed gap: downloaded Node 20.19.1 Linux x64 into `$HOME/tools` (no system install allowed) and u…
- Tests: full suite `npm test` exit 0 → `1292 passing, 5 pending, 0 failing` (also machine-read as …
- End-to-end: installed the built package into a scratch project, `hexo init` (cloned starter), `he…
- Errors hit: (1) tests failed on Node 18 — fixed by using Node 20.19.1; (2) 4 asset-suite failures…
## ARGUSIC_RESULT
{"install_succeeded":true,"launch_succeeded":true,"install_minutes":33,"errors":[{"msg":"Node 18.19…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 3 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 33 minutes to install, slower than the median of the 11 comparable projects Argusic has measured.
Of the 12 hacktoberfest projects Argusic has installed and timed, hexo was the 11th fastest to reach a running state, and 11 of 12 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.
Run history
Topics (from GitHub)
hacktoberfesthexojavascriptnodejsstatic-site-generatortypescript
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/hexo)Questions
- Does hexo run?
- Yes. hexo runs. Argusic installed and launched it on a clean machine in 33 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test hexo?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 751e856691bf. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test hexo?
- The run that produced this verdict cost $0.65: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does hexo take to install?
- 33 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 hexo need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing hexo?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does hexo compare with the alternatives?
- Of the 12 hacktoberfest projects Argusic has installed and timed, hexo was the 11th fastest to reach a running state, and 11 of 12 reached one at all.
- Where is the evidence for hexo?
- 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.