hexo-theme-stellar
基于 Hexo 的全能个人知识库，开箱即用，内置海量标签和动态数据组件。可用于个人博客、项目文档、知识库、专栏、笔记等。
Runssource: GitHubhomepageJavaScriptMITcommit 402e9586be07
JavaScript, MIT licensed. The project labels itself: hexo, hexo theme, hexo theme stellar, ready for agent, stellar and wiki.
hexo-theme-stellar runs. An Argusic agent installed it in 0.5 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
npm install, lint, all 241 unit tests, reuse contract checks, contribution registry checks, and all 4 integration scenarios (post-topic, notebook, wiki, default-content) pass on Node v22.11.0
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.
- Integration test failed: Hexo 8.1.2 depends on strip-ansi@^7.1.0 which is ESM-only, but Hexo uses require() to load it (ERR_REQUIRE_ESM)5 minutes
- Node.js v18.19.1 below project requirement (>=22)0.3 minutes
- Install time
- under a minute
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- npm run check exited 0 (lint pass, 241 unit tests pass, reuse check pass, contributions check pass); npm run integration:check exited 0 (3 scenarios + default-content: doctor/generate/routes/search pass, preview server HTTP 200 pass, minify/ESM preservation pass)
- Model tokens used
- 59,592
- Exact commit tested
- 402e9586be07
- 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.
59,592 All checks pass end-to-end. Let me now report the final results. **Summary of what was done:** 1. **Installed Node.js v22.11.0** — the system had v18.19.1 but the project requires >=22. Download… 2. **Installed npm dependencies** — `npm install` succeeded (190 packages, 0 errors). 3. **Identified and fixed Hexo 8 ESM incompatibility** — The integration test (`ci/check-package-in… 4. **Verified full suite:** - `npm run lint` — pass (0 issues) - `npm run test:unit` — 241/241 tests pass, reuse check passes, agent docs check passes - `npm run contributions:check` — 25 descriptors verified - `npm run check` (lint + test) — all pass - `node ci/check-package-integration.js` — all 3 scenarios (post-topic/en, notebook/zh-CN, wiki/…
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 0.5 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.
- A quick evaluation: it was running 0.5 minutes after the clone.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/hexo-theme-stellar)Questions
- Does hexo-theme-stellar run?
- Yes. hexo-theme-stellar runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test hexo-theme-stellar?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 402e9586be07. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test hexo-theme-stellar?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does hexo-theme-stellar take to install?
- 0.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 hexo-theme-stellar need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing hexo-theme-stellar?
- 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 hexo-theme-stellar?
- 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.