lxc/incus-compose scored 10/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 repetition4/8 files · 30%
Near-duplicate blocks with small edits instead of a shared helper.
- Boilerplate padding1/8 files · 22%
More lines, wrappers and ceremony than the job needs.
- Unused or phantom imports1/8 files · 21%
Imports that are never used, or calls to APIs that don't seem to exist.
- Defensive everything1/8 files · 7%
Blanket try/catch, log-and-rethrow, impossible null checks.
Human fingerprints
- Domain-specific naming8/8 files · 63%
Names that show deep familiarity with the problem.
- Pragmatic shortcuts8/8 files · 41%
Terse idioms and deliberate omissions an experienced author takes.
- Lived-in code5/8 files · 39%
Idiosyncrasies and quirks of code that evolved over time.
- Comments explain why5/8 files · 35%
Comments about trade-offs, gotchas, bugs and workarounds.
Files we looked at
The files behind the score, sloppiest first.
- cmd/incus-compose/down_test.go25out of 100
Go · 5.2 KB
- Copy-paste repetition 44%
- Boilerplate padding 33%
- iclient/incus_certificate.go15out of 100
Go · 1.7 KB
- client/resource_instance.go10out of 100
Go · 59 KB
- ievent/debounce/debounce.go9out of 100
Go · 6.1 KB
- Copy-paste repetition 32%
- project/instance.go3out of 100
Go · 53 KB
- Copy-paste repetition 44%
- cmd/ic-dns/chain.go3out of 100
Go · 6.4 KB
- cmd/ic-dns/dns/serve.go1out of 100
Go · 4.2 KB
- Defensive everything 31%
- cmd/ic-healthd/checker/instance.go0out of 100
Go · 28 KB
- Unused or phantom imports 33%
- Copy-paste repetition 33%
Scanned Oct 30, 2026 from develop. A playful gut check, not a verdict on the people behind the code. How scoring works. More recent reports.