mermaid-rs-renderer

A fast native Rust Mermaid diagram renderer. No browser required. 500-1000x faster than mermaid-cli.

Runssource: GitHubRustMITcommit 3726ccbffe0e

Rust, MIT licensed. The project labels itself: cli, diagram, flowchart, mermaid, rust and svg.

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

The mermaid-rs-renderer (mmdr) crate builds with cargo, 386 lib unit tests pass, all integration test suites pass, the CLI can pipe stdin to SVG or PNG output, and input of at least flowchart, sequence, class, state, pie, and radar diagram types render correctly.

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.24 (measured)
recorded runs
2
last tested
stars
1,825
forks
115
open issues
62
watchers
6
size
24 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 mermaid-rs-renderer, 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.

  • Quadrant chart label overflow bug: label bbox at y=0 (top edge) extended above canvas because vertical overflow was not accounted for7 minutes
Install time
36 minutes
Cold machine to finish
38 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
mmdr -e svg produced valid SVG from 'flowchart LR; A-->B-->C' stdin (viewBox present, valid XML); mmdr -e png produced valid 2045-byte PNG verified by ffmpeg -v error -i FILE -f null -, exit 0; cargo test --lib passed 386/386; cargo test --test layout_suite passed 28/28; cargo test --test cli_suite passed 9/9
Model tokens used
540,585
Exact commit tested
3726ccbffe0e
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.

Now let me compute total installation time.
exec
/bin/sh -lc 'echo "Install started at ~10:16 (rustup install). First build finished around 10:18. L…
 succeeded in 0ms:
Install started at ~10:16 (rustup install). First build finished around 10:18. Let me check git log…
3726ccb Add optional renderer-neutral native vector scene API
Here is the final report:
2026-11-13T10:54:40.290819Z ERROR codex_core::session: failed to record rollout items: thread 01a1d…
2026-11-13T10:54:40.290872Z ERROR codex_core::session: failed to record rollout items: thread 01a1d…
tokens used
540,585
Here is 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.
  • 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 36 minutes to install, slower than the median of the 126 comparable projects Argusic has measured.

Of the 127 cli projects Argusic has installed and timed, mermaid-rs-renderer was the 126th fastest to reach a running state, and 115 of 127 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/3Runs100.000.24
Argusic Runner1/3Runs100.000.21

Topics (from GitHub)

clidiagramflowchartmermaidrustsvg

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/mermaid-rs-renderer.svg)](https://argusic.com/subject/mermaid-rs-renderer)

Questions

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