What stood out

How strongly each pattern showed up overall, and in how many of the files.

Boilerplate padding3/8 files · 24%
More lines, wrappers and ceremony than the job needs.
Needless abstraction1/8 files · 16%
Classes, interfaces or factories with a single trivial use.
Defensive everything1/8 files · 6%
Blanket try/catch, log-and-rethrow, impossible null checks.

Domain-specific naming7/8 files · 47%
Names that show deep familiarity with the problem.
Pragmatic shortcuts8/8 files · 41%
Terse idioms and deliberate omissions an experienced author takes.
Lived-in code4/8 files · 33%
Idiosyncrasies and quirks of code that evolved over time.
Comments explain why3/8 files · 27%
Comments about trade-offs, gotchas, bugs and workarounds.

Files we looked at

The files behind the score, sloppiest first.

lib/generators/view_component/component/component_generator.rb27out of 100
Ruby · 2.3 KB
- Boilerplate padding 32%
app/controllers/view_components_system_test_controller.rb26out of 100
Ruby · 1.1 KB
- Defensive everything 35%
- Boilerplate padding 31%
performance/compare.rb22out of 100
Ruby · 2.3 KB
- Boilerplate padding 32%
script/regression_check.rb18out of 100
Ruby · 17 KB
- Needless abstraction 33%
lib/view_component/serializable/proxy.rb14out of 100
Ruby · 3.5 KB
lib/view_component/base.rb10out of 100
Ruby · 32 KB
lib/view_component/slot.rb9out of 100
Ruby · 3.9 KB
lib/view_component/cache_digest/resolver.rb0out of 100
Ruby · 10 KB

Scanned Oct 31, 2026 from main. A playful gut check, not a verdict on the people behind the code. How scoring works. More recent reports.