Calculate · Assess & Decide · Engineering
Defect density per module with ranked hotspots
Defect density per module against your chosen size unit, the overall density, and a ranking of the most defect-dense modules.
You receive: A reviewed defect-density calculator + the passing test report, run on your module defect and size counts.
Part of Ship MVP
Example
A sample of what this play produces. Your result is generated for your inputs.
- Overall density
- 0.85
| Rank | Name | Density |
|---|---|---|
| 1 | platform/src/lib | 1.94 |
| 2 | platform/src/app | 1.45 |
| 3 | platform/src/components | 1.05 |
| 4 | platform/src/db | 0.58 |
| 5 | judge/stud_judge | 0.42 |
Inputs
- Modules
Name Size Defects platform/src/app 12400 18 platform/src/components 8600 9 platform/src/db 5200 3 judge/stud_judge 26000 11 platform/src/lib 3100 6 - Size unit
- KLOC
- Per scale
- 1
- Rank order
- desc
- Rounding dp
- 2
Arithmetic recomputed against the tasks.py compute_defect_density oracle, 2026-08-08, on the modules of STUD's own codebase (defect counts illustrative): per KLOC, app 18/12.4 = 1.45, components 9/8.6 = 1.05, db 3/5.2 = 0.58, judge 11/26 = 0.42, lib 6/3.1 = 1.94; overall 47 defects over 55.3 KLOC = 0.85. Ranked descending, platform/src/lib is the hotspot at 1.94 defects per KLOC, more than twice the overall density.
Opens soon
STUD opens runs for everyone soon, on every play at once.
Scope of the check
What's verified: STUD verifies the calculator computes defect density per module on held-out cases: defects divided by size (LOC, or LOC/1000 for KLOC) times your per-scale, the overall density across the totals, and the ranking with name-ascending tie-breaks. STUD does NOT count real defects or lines for you, nor judge whether a module's density is acceptable; it checks the arithmetic on the counts you provide.
Get early access to STUD the day it goes live.