graphviz-visual-editor

A web application for interactive visual editing of Graphviz graphs described in the DOT language.

Runssource: GitHubJavaScriptMITcommit 4823bcd2ee1e

JavaScript, MIT licensed. The project labels itself: dot, graph drawing, graph view, graph visualization, graphviz, graphviz dot language, graphviz viewer and interactive visualization.

graphviz-visual-editor runs. An Argusic agent installed it in 2 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

graphviz-visual-editor installs cleanly, all 634 unit tests pass, and the production build compiles successfully with only deprecation warnings.

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.02 (measured)
recorded runs
1
last tested
stars
818
forks
0
open issues
0
watchers
0
created
-
last push
-

Subject data from GitHub, linked at the top of this page. 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.

Install time
2 minutes
Cold machine to finish
2 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
CI=true npm test: 1 suite passed, 634 tests passed; npm run build: compiled successfully
Model tokens used
22,125
Exact commit tested
4823bcd2ee1e
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.

-rw-rw-r-- 1 runner runner     60 Nov 20 07:16 src/graphvizVersion.js
-rw-rw-r-- 1 runner runner  51079 Nov 20 07:16 src/shapes.js
-rw-rw-r-- 1 runner runner   1065 Nov 20 07:16 src/versions.json
exec
/bin/sh -lc 'cd /work/repo && cat build/index.html 2>/dev/null | head -3' in /work/repo
 succeeded in 0ms:
<!doctype html><html lang="en" dir="ltr"><head><meta charset="utf-8"><meta name="viewport" content=…
All steps completed successfully with zero errors. Here's the result:
2026-11-20T07:18:07.401489Z ERROR codex_core::session: failed to record rollout items: thread 01a1f…
tokens used
22,125
All steps completed successfully with zero errors. Here's the result:

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 minutes.
  • Nothing broke on the way: zero errors between clone and running.
  • 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 2 minutes after the clone.
  • Following its own README: the documented path worked with nothing to fix.

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 Runner1/3Runs100.000.02

Topics (from GitHub)

dotgraph-drawinggraph-viewgraph-visualizationgraphvizgraphviz-dot-languagegraphviz-viewerinteractive-visualizationjavascripttext-editorvisual-editorweb-applicationwysiwygwysiwyg-editor

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/graphviz-visual-editor.svg)](https://argusic.com/subject/graphviz-visual-editor)

Questions

Does graphviz-visual-editor run?
Yes. graphviz-visual-editor runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test graphviz-visual-editor?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4823bcd2ee1e. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test graphviz-visual-editor?
The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does graphviz-visual-editor take to install?
2 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 graphviz-visual-editor need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing graphviz-visual-editor?
Nothing did, in the recorded run: zero errors between clone and running.
Where is the evidence for graphviz-visual-editor?
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.

Discussion