thulite
Web framework designed for speed, security, and SEO, all powered by Hugo and npm.
Runssource: GitHubhomepageJavaScriptMITcommit 1a445c196ad3
JavaScript, MIT licensed. The project labels itself: framework, hugo, npm, static site generator and thulite.
thulite runs. An Argusic agent installed it in 4 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Hugo extended 0.166.0, Dart Sass 1.104.1, and Node 24.0.0 produce a working build (3 pages, fingerprinted CSS+JS) and a dev server that answers HTTP 200.
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.
- Hugo extended binary not found on system1 minute
- Dart Sass not found on system1 minute
- Node.js v18 on PATH is too old; Hugo 0.166.0's PostCSS pipeline passes --permission and --allow-fs-read flags to node, which only exist in Node 23+1 minute
- Install time
- 4 minutes
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- hugo --gc --minify exited 0 producing 3 pages; curl http://localhost:1313/ returned HTTP 200 with expected HTML body containing 'Thulite'
- Model tokens used
- 58,186
- Exact commit tested
- 1a445c196ad3
- 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 attempt that decided the verdict above. 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.
/bin/sh -lc '# compute time estimate for record
echo "Start: $(stat -c%Z /work/repo/README.md 2>/dev/null || echo 0)"
echo "Now: $(date +%s)"' in /work/repo
succeeded in 0ms:
Start: 1792643555
Now: 1792643770
All done. Here's the report:
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 4, "er…
tokens used
58,186
All done. Here's the report:
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 4, "er…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 4 minutes.
- 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.
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 4 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
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/thulite)Questions
- Does thulite run?
- Yes. thulite runs. Argusic installed and launched it on a clean machine in 4 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test thulite?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1a445c196ad3. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test thulite?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does thulite take to install?
- 4 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 thulite need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing thulite?
- 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.
- Where is the evidence for thulite?
- 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.