rumdl

Fast Markdown linter and formatter written in Rust

Runssource: GitHubRustNOASSERTIONcommit 21246a6a1c9f

Rust, NOASSERTION licensed. The project labels itself: cli, developer tools, formatter, linter, markdown and rust.

rumdl runs. An Argusic agent installed it in 0.0 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

rumdl 0.3.4 is installed and fully functional from /home/runner/.local/bin/rumdl: linting (check), formatting (fmt), auto-fix, config generation and reading, rule documentation, schema generation, and shell completions all work correctly on the repo markdown 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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.03 (measured)
recorded runs
2
last tested
stars
1,688
forks
99
open issues
10
watchers
8
size
28 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.

Install time
under a minute
Cold machine to finish
1 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
rumdl --version returned rumdl 0.3.4; rumdl check README.md returned 'Success: No issues found in 1 file (35ms)'; rumdl check /tmp/test_rumdl.md caught MD024 duplicate-heading error with exit code 1; rumdl fmt --check docs/ returned 'Success: No issues found in 22 files (48ms)'; rumdl init/config/rule/explain/schema/completions all produced valid output
Model tokens used
82,166
Exact commit tested
21246a6a1c9f
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.

- `rumdl completions bash` → generated shell completions
No errors encountered during installation or operation. No third-party keys or network services nee…
exec
/bin/sh -lc "echo 'ARGUSIC_RESULT: {\"install_succeeded\": true, \"launch_succeeded\": true, \"inst…
 succeeded in 0ms:
exec
/bin/sh -lc 'cd /work/repo && git status --short 2>&1' in /work/repo
 succeeded in 0ms:
No changes to the repository were made. The install was clean — only the binary in the user's pip d…
tokens used
82,166
No changes to the repository were made. The install was clean — only the binary in the user's pip d…

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 0.0 minutes, faster than the median of the 126 comparable projects Argusic has measured.
  • Nothing broke on the way: zero errors between clone and running.
  • Ran without a GPU, so it does not need one to start.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Its license file could not be classified automatically, so check it yourself before using it.

Of the 127 cli projects Argusic has installed and timed, rumdl was the 2nd 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.
  • A quick evaluation: it was running 0.0 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 Runner2/3Runs100.000.03
Argusic Runner1/3Runs100.000.09

Topics (from GitHub)

clideveloper-toolsformatterlintermarkdownrust

Embed the badge

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

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

Questions

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