html5-boilerplate

A professional front-end template for building fast, robust, and adaptable web apps or sites.

Runssource: GitHubhomepageJavaScriptMITcommit b6597338e695

JavaScript, MIT licensed. The project labels itself: best practices, css, html, html5, html5 boilerplate, javascript and robust.

html5-boilerplate runs. An Argusic agent installed it in 0.1 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

npm install, npm run build, npm run lint all succeed. npm test passes all 25 tests. Archive zip is produced with 19 files.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.01 (measured)
recorded runs
2
last tested
stars
57,695
forks
12,222
open issues
14
watchers
2,443
size
22 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 html5-boilerplate, 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.

  • mocha 12 requires Node >=22 (container has Node 18.19) — 'with { type: "json" }' syntax error0.5 minutes
Install time
under a minute
Cold machine to finish
1 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
npm test exited 0, 25 passing (spec reporter, 10ms); npm run build exited 0; npm run lint exited 0
Model tokens used
18,154
Exact commit tested
b6597338e695
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.

css/style.css
All 25 tests pass, lint is clean, and the build/archive produce correct output. Let me record the r…
exec
/bin/sh -lc "cat << 'EOF'
EOF" in /work/repo
 succeeded in 0ms:
```json
```
tokens used
18,154
```json
```

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.1 minutes.
  • Recovered from all 1 error 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 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.1 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.01
Argusic Runner1/3Runs100.000.01

Topics (from GitHub)

best-practicescsshtmlhtml5html5-boilerplatejavascriptrobust

Embed the badge

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

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

Questions

Does html5-boilerplate run?
Yes. html5-boilerplate runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test html5-boilerplate?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit b6597338e695. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test html5-boilerplate?
The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does html5-boilerplate take to install?
0.1 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 html5-boilerplate need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing html5-boilerplate?
1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for html5-boilerplate?
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