wavedrom

:ocean: Digital timing diagram rendering engine

Runssource: GitHubhomepageJavaScriptMITcommit 142dd41870bc

JavaScript, MIT licensed. The project labels itself: diagram, hacktoberfest and svg.

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

WaveDrom 3.7.0 builds and runs with Node 20; CLI accepts --input/--indent/--version/--help and generates SVG from JSON5 files; all 6 mocha tests pass; 4 browser bundles (wavedrom.js, wavedrom.min.js, wavedrom.unpkg.js, wavedrom.unpkg.min.js) built successfully; no third-party credentials required.

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.04 (measured)
recorded runs
2
last tested
stars
3,522
forks
424
open issues
209
watchers
88
size
1 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 wavedrom, 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.

  • system Node.js v18.19.1 is below project minimum >=20; npm install fails at runtime with ESM import errors1.5 minutes
Install time
3 minutes
Cold machine to finish
2 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
npm test passed 6/6, wavedrom --version returned 3.7.0, wavedrom --input test/signal-step4.json5 produced valid <svg> containing waveform elements, wavedrom --input test/reg-vl.json5 produced valid <svg> containing register diagram
Model tokens used
35,200
Exact commit tested
142dd41870bc
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.

3.7.0
=== CLI GENERATES SVG ===
1
=== BUILD ARTIFACTS ===
-rw-rw-r-- 1 runner runner 140434 Nov  9 13:18 wavedrom.js
-rw-rw-r-- 1 runner runner  55206 Nov  9 13:18 wavedrom.min.js
-rw-rw-r-- 1 runner runner 191514 Nov  9 13:18 wavedrom.unpkg.js
-rw-rw-r-- 1 runner runner  98952 Nov  9 13:18 wavedrom.unpkg.min.js
All checks passed — here's the summary. One issue encountered: the container ships Node 18 but the …
tokens used
35,200
All checks passed — here's the summary. One issue encountered: the container ships Node 18 but the …

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 2.5 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.

Of the 14 diagram projects Argusic has installed and timed, wavedrom was the 7th fastest to reach a running state, and 11 of 14 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 2.5 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.04
Argusic Runner1/3Runs100.000.02

Topics (from GitHub)

diagramhacktoberfestsvg

Embed the badge

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

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

Questions

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