lxc/incus scored 15/100 on Slopicide
Handcrafted
Artisanal, small-batch code. A human clearly sweated over this.
What stood out
How strongly each pattern showed up overall, and in how many of the files.
- Copy-paste repetition2/8 files · 26%
Near-duplicate blocks with small edits instead of a shared helper.
- Unused or phantom imports1/8 files · 21%
Imports that are never used, or calls to APIs that don't seem to exist.
- Boilerplate padding1/8 files · 20%
More lines, wrappers and ceremony than the job needs.
Human fingerprints
- Domain-specific naming8/8 files · 66%
Names that show deep familiarity with the problem.
- Lived-in code6/8 files · 51%
Idiosyncrasies and quirks of code that evolved over time.
- Pragmatic shortcuts7/8 files · 41%
Terse idioms and deliberate omissions an experienced author takes.
- Comments explain why3/8 files · 32%
Comments about trade-offs, gotchas, bugs and workarounds.
Files we looked at
The files behind the score, sloppiest first.
Go · 597 B
- internal/server/db/cluster/networks_zones.go38out of 100
Go · 2.7 KB
- Unused or phantom imports 33%
- internal/server/metrics/types.go16out of 100
Go · 20 KB
- cmd/incusd/api_vsock.go11out of 100
Go · 1.3 KB
- cmd/incus/exec_windows.go7out of 100
Go · 1.4 KB
- Boilerplate padding 33%
- cmd/incusd/images.go0out of 100
Go · 143 KB
- Copy-paste repetition 43%
Go · 120 KB
Go · 118 KB
- Copy-paste repetition 37%
Scanned Oct 30, 2026 from main. A playful gut check, not a verdict on the people behind the code. How scoring works. More recent reports.