fallow
Codebase intelligence for TypeScript and JavaScript. Health, complexity hotspots, duplication, architecture boundaries, circular dependencies, design-system drift, and unused code, from one graph. CLI, GitHub Action, LSP, MCP, and VS Code. Rust, MIT licensed.
Runssource: GitHubhomepageRustMITcommit 86482cc66fe9
Rust, MIT licensed. The project labels itself: architecture, circular dependencies, cli, code duplication, code health, code quality, codebase intelligence and complexity.
fallow runs. An Argusic agent installed it in 57 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Fallow CLI installs via npm and cargo build, runs on this repo producing valid analysis output, and passes 17018 tests across all workspace crates.
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.
- Node.js 18 lacks Array.toSorted() causing fallow-type-aware sidecar failures in 2 tests3 minutes
- cargo test --release p fallow-cli killed by SIGKILL from LTO+release memory2 minutes
- No Rust toolchain installed1 minute
- Install time
- 57 minutes
- Cold machine to finish
- 58 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- cargo test --workspace exited 0 with 17018 passed; npx fallow --version returned 'fallow 3.28.0 verified: yes'; fallow health --format json --quiet produced valid health JSON in 629ms
- Model tokens used
- 587,268
- Exact commit tested
- 86482cc66fe9
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
All done. Here's the summary: The session took about 57 minutes. I installed Rust from scratch, the npm package, built the binary… **What was verified:** - `npx fallow --version` → `fallow 3.28.0` (verified npm binary) - `/work/repo/target/release/fallow --version` → `fallow 3.27.0` (source-built binary) - `fallow health --format json --quiet` → valid health JSON with 629ms analysis time on this repo - `cargo test -p fallow-cli` → 4333 passed, 0 failed - `cargo test --workspace` → 17,018 passed, 0 failed (debug profile) **Errors encountered and fixed:** 1. Node.js 18 lacked `Array.toSorted()` causing 2 fallow-type-aware test failures → installed Node … 2. No Rust installed → installed rustup + rust 1.97.1 3. `cargo test --release` OOM-killed (SIGKILL from LTO+release memory pressure) → used debug profile
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 3 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 3 times, so the result is not a one-off.
What did not, or is not known
- Took 57 minutes to install, slower than the median of the 123 comparable projects Argusic has measured.
Of the 124 cli projects Argusic has installed and timed, fallow was the 123rd fastest to reach a running state, and 111 of 124 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
Topics (from GitHub)
architecturecircular-dependenciesclicode-duplicationcode-healthcode-qualitycodebase-intelligencecomplexitydead-codedeveloper-toolsjavascriptmcpmonorepooxcruststatic-analysistypescriptunused-code
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/fallow)Questions
- Does fallow run?
- Yes. fallow runs. Argusic installed and launched it on a clean machine in 57 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test fallow?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 86482cc66fe9. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test fallow?
- The run that produced this verdict cost $0.16: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does fallow take to install?
- 57 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 fallow need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing fallow?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does fallow compare with the alternatives?
- Of the 124 cli projects Argusic has installed and timed, fallow was the 123rd fastest to reach a running state, and 111 of 124 reached one at all.
- Where is the evidence for fallow?
- All 3 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.