goplantuml
PlantUML Class Diagram Generator for golang projects
Runssource: GitHubGoMITcommit 81d136b30c93
Go, MIT licensed. The project labels itself: diagram, diagram generator, go, golang, plantuml and uml diagram.
goplantuml runs. An Argusic agent installed it in 5 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
GoPlantUML builds with Go 1.22.2, installs as a goplantuml binary, all 46 parser tests pass, and the binary runs against real Go source directories to emit valid PlantUML diagrams to stdout and files.
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
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.
- Go toolchain not installed in container (no go binary found)5 minutes
- Install time
- 5 minutes
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- go test -count=1 ./parser/ exited 0 (ok github.com/jfeliu007/goplantuml/parser 0.008s, 46 tests, 0 failures); /tmp/gopath/bin/goplantuml /work/repo/parser exited 0 and emitted valid PlantUML output bounded by @startuml/@enduml; goplantuml -h exited 0 and printed usage
- Model tokens used
- 152,222
- Exact commit tested
- 81d136b30c93
- 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.
tokens used 152,222 Everything is verified. Let me now compose the final result JSON. Summary of the work: 1. **Error**: Go toolchain not installed in container. - **Fix**: Downloaded Go 1.22.2 Debian packages (golang-1.22-go, golang-1.22-src, golang-src, go… 2. **Install**: `go build ./...` exited 0, `go install ./cmd/goplantuml` exited 0 3. **Launch/verify**: Ran `/tmp/gopath/bin/goplantuml /work/repo/parser` — output valid PlantUML wi… 4. **Tests**: `go test -count=1 ./parser/` → `ok ... 0.008s`, 46 tests passing (108 PASS lines incl… 5. **test_depth**: tier1_real — real behavior verified end-to-end (binary produced actual PlantUML … 6. **verified_how**: `go test -count=1 ./parser/` returned `ok github.com/jfeliu007/goplantuml/pars… This is a CLI tool, not a desktop app. It needs no third-party keys.
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 5 minutes, faster than the median of the 3 comparable projects Argusic has measured.
- 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.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 4 diagram projects Argusic has installed and timed, goplantuml was the 2nd fastest to reach a running state, and 4 of 4 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.
- A quick evaluation: it was running 5 minutes after the clone.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/goplantuml)Questions
- Does goplantuml run?
- Yes. goplantuml runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test goplantuml?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 81d136b30c93. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test goplantuml?
- 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 goplantuml take to install?
- 5 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 goplantuml need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing goplantuml?
- 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 goplantuml compare with the alternatives?
- Of the 4 diagram projects Argusic has installed and timed, goplantuml was the 2nd fastest to reach a running state, and 4 of 4 reached one at all.
- Where is the evidence for goplantuml?
- 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.