pintora

An extensible text-to-diagrams library that works in both browser and node.js

Runssource: GitHubhomepageTypeScriptMITcommit 695eb2ed2246

TypeScript, MIT licensed. The project labels itself: diagram, diagram as code and mermaidjs.

pintora runs. An Argusic agent installed it in 16 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Installs, compiles, and runs test suite (38 suites, 227 tests, 26 snapshots all passing). CLI can render diagrams to SVG via jsdom+bundled pintora-standalone.

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

At a glance

verdict
Runs
Argusic Score
75 / 100
cost of the verifying run
$0.17 (measured)
recorded runs
2
last tested
stars
1,282
forks
39
open issues
45
watchers
10
size
11 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 pintora, 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.

  • jsdom@29 dep [email protected] requires Node 20+6 minutes
  • rolldown requires Node 20+ (node:util/styleText)4 minutes
Install time
16 minutes
Cold machine to finish
25 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
pnpm test exited 0, 38 suites/227 tests/26 snapshots all passed; CLI renderToSvg produces valid SVG (length=4026, contains <svg> and </svg>) for sequence diagram
Model tokens used
173,644
Exact commit tested
695eb2ed2246
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.

- CLI SVG renderer produces valid `<svg>` output for sequence and ER diagrams
tokens used
173,644
All verified. Here's a clean final summary of the work done.
**Problems found and fixed:**
1. **`@pintora/standalone` rolldown build** needed `node:util/styleText` (Node 20+). Fixed by switc…
2. **`jsdom@29`** transitively required `[email protected]` and `@exodus/[email protected]`, both…
**Verification:**
- `pnpm install` — 2285 packages, done
- `pnpm compile` — 9/9 tasks successful
- `pnpm test` — 38 suites, 227 tests, 26 snapshots, all passed
- CLI SVG renderer produces valid `<svg>` output for sequence and ER diagrams

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 2 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 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 16 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, pintora was the 12th 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/3Did not run50.000.06
Argusic Runner1/3Runs100.000.17

Topics (from GitHub)

diagramdiagram-as-codemermaidjs

Embed the badge

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

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

Questions

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