drawthe.net

drawthe.net draws network diagrams dynamically from a text file describing the placement, layout and icons. Given a yaml file describing the hierarchy of the network and it's connections, a resulting diagram will be created.

Runssource: GitHubTypeScriptMITcommit c71cdba4c3bd

TypeScript, MIT licensed. The project labels itself: diagram, icons and network.

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

On a brand-new clone, npm ci, npm run build, and npm run render all succeed and the app runs in a real browser and through its MCP server.

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 90 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
90 / 100
cost of the verifying run
$0.07 (measured)
recorded runs
2
last tested
stars
1,182
forks
134
open issues
7
watchers
54
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 drawthe.net, 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.

  • CLI renderer crashed in d3-zoom: ReferenceError: navigator is not defined (node 18/jsdom headless render)18 minutes
Install time
26 minutes
Cold machine to finish
8 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
npm run render -- examples/NTP.yaml out.svg printed 'Wrote out.svg'; resvg decoded the SVG to a PNG and ffmpeg -v error -i <png> exited 0; Chromium loaded render.html?doc=sample (200, title set, 56 paths/33 texts, 0 console errors); MCP tools/call render_diagram returned SVG+PNG over stdio
Model tokens used
306,487
Exact commit tested
c71cdba4c3bd
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.

- `npm run render -- examples/NTP.yaml out.svg` printed `Wrote out.svg`; produced 458,304-byte stan…
- Vite dev server stayed up and answered 200 on `/`, `/fullscreen.html`, `/render.html`, `render.ht…
- Real headless Chromium on `render.html?doc=sample`: status 200, page title `drawthe.net: Sample D…
- Editor page `index.html`: status 200, Ace editor loaded with 50 lines, then inserted YAML and cli…
- Popup `fullscreen.html` fed via `window.opener.design`: rendered SVG (1262 paths) titled `dld4e: …
- MCP server over stdio JSON-RPC: initialize handshake OK; `render_diagram` returned valid SVG and …
- `npm run lint`, `npm run typecheck`, `npm run build` all exited 0 after the fix.
- Fresh pristine clone of the repo (without my fix) reproduced the same `navigator` crash; with the…
**Notes**
- Environment Node is v18.19.1 (README requests 20+); everything works on 18 after the fix — noted …
- repo has no automated test suite, and no auth keys were required (MCP/rendering are fully local),…
`ARGUSIC_RESULT: {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 26, "erro…

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 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 did not, or is not known

  • Took 26 minutes to install, slower than the median of the 13 comparable projects Argusic has measured.

Of the 14 diagram projects Argusic has installed and timed, drawthe.net was the 14th 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.

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/3Unverified80.000.05
Argusic Runner1/3Runs100.000.07

Topics (from GitHub)

diagramiconsnetwork

Embed the badge

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

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

Questions

Does drawthe.net run?
Yes. drawthe.net runs. Argusic installed and launched it on a clean machine in 26 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test drawthe.net?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit c71cdba4c3bd. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test drawthe.net?
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 drawthe.net take to install?
26 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 drawthe.net need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing drawthe.net?
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 drawthe.net compare with the alternatives?
Of the 14 diagram projects Argusic has installed and timed, drawthe.net was the 14th fastest to reach a running state, and 11 of 14 reached one at all.
Where is the evidence for drawthe.net?
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