Cargo-Crap: Finding Untested Complexity in AI-Generated Rust Code
The article discusses the creation of cargo-crap, a tool designed to assess the safety of changing AI-generated Rust code. It introduces the Change Risk Anti-Patterns (CRAP) metric, which combines cyclomatic complexity and test coverage to identify risky code. The tool aims to provide measurable checks around the complexity introduced by AI agents in software development.
- ▪Cargo-crap is an open-source tool that identifies complex and poorly tested functions in Rust code.
- ▪The CRAP metric combines cyclomatic complexity and test coverage to highlight code that is risky to change.
- ▪The tool serves as a guardrail for AI-assisted Rust development, making untested complexity visible.
2 outlets in our directory ran this story. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
Hacker News (AI / LLM) files mainly under ai. We currently carry 9,489 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Minikin |
| Canonical URL | https://minikin.me/blog/cargo-crap |
| Publication time | Mon, 18 May 2026 16:55:29 +0000 |
| Retrieval time | 2026-05-18T16:59:56.636Z |
| Last seen | 2026-05-18T16:59:56.636Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | z6m3nsUNRoRd · 2 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
May 13, 2026 12 min read cargo-crap: Finding Untested Complexity in AI-Generated Rust Code v0.2.0 cargo-crap is open source. Try it, star it, or read the docs. GitHub crates.io docs.rs Rust makes many bugs impossible. Memory safety. Thread safety. Ownership. Lifetimes. Exhaustive matching. Strong types. But Rust cannot answer one essential maintenance question: Is this code safe to change? A function can compile perfectly and still be risky to touch. It can have too many branches, too many special cases, too many hidden paths, and not enough tests to give you confidence. This is why I built cargo-crap is a Rust tool that finds functions that are both complex and poorly tested by calculating the Change Risk Anti-Patterns (CRAP) metric.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Minikin.