joint
A proven SVG-based JavaScript diagramming library powering exceptional UIs
Runssource: GitHubhomepageJavaScriptMPL-2.0commit 881e49d8f5e4
JavaScript, MPL-2.0 licensed. The project labels itself: charts, diagramming, html5, interactive diagrams, javascript, javascript library, low code and no code.
joint runs. An Argusic agent installed it in 2.1 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
After patching 4 rollup configs for Node 18 compatibility and running builds, the JointJS monorepo installs, builds, and runs tests across @joint/core (2112/2113 Karma + 4/4 Node + 2 TS checks), @joint/cli (20/20), @joint/layout-directed-graph (22/22), and @joint/vitest-plugin-mock-svg (2/2); the core library loads and produces correct diagram output (Graph, elements, links, geometry all verified working).
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
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.
- Rollup configs use `import ... with { type: 'json' }` syntax requiring Node 22+, but Node 18.19.1 is available. The syntax causes `SyntaxError: Unexpected token 'with'` in 4 packages: @joint/layout-directed-graph, @joint/layout-msagl, @joint/router-avoid, @joint/react.2 minutes
- Server tests failed because `build/joint.js` did not exist yet — the project requires building before testing.1 minute
- 1 pre-existing test failure in @joint/core: `util > util.breakText takes in account international characters` fails due to font-metric differences in Chrome 140 — CJK characters break at different positions than the expected values. 2112/2113 pass overall.
- @joint/react Jest tests: 31 suites failed (113 tests) out of 100 suites (1065 tests) — likely Node 18 incompatibility with React 19's renderToPipeableStream. Not investigated further as it requires Node 22.
- Install time
- 2 minutes
- Cold machine to finish
- 22 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- `yarn test` across all packages: @joint/cli 20/20 pass, @joint/core 4/4 server + 2 TS typechecks + 2112/2113 Karma browser tests pass (1 pre-existing CJK breakText failure), @joint/layout-directed-graph 22/22 pass, @joint/vitest-plugin-mock-svg 2/2 pass; also `node -e 'require("./build/joint.min.js").dia.Graph' loaded Graph+shapes+geometry correctly
- Model tokens used
- 296,310
- Exact commit tested
- 881e49d8f5e4
- 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.
console.log('All checks passed');
\"" in /work/repo
succeeded in 45ms:
Graph cells: 1 - post at: { x: 10, y: 20 }
Link added, total cells: 2
g.Point: 10 20
Export count: 22
All checks passed
All tests are done. Here's the final report.
tokens used
296,310
All tests are done. Here's the final report.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.1 minutes.
- Recovered from all 4 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 MPL-2.0, 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 2.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
Topics (from GitHub)
chartsdiagramminghtml5interactive-diagramsjavascriptjavascript-librarylow-codeno-codesvgtypescripttypescript-libraryvisual-applicationsvisualization
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/joint)Questions
- Does joint run?
- Yes. joint runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test joint?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 881e49d8f5e4. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test joint?
- The run that produced this verdict cost $0.18: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does joint take to install?
- 2.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 joint need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing joint?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for joint?
- 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.