Code quality
The static health of the source: TypeScript strict mode, an error-free lint run, how far the tolerated lint-warning count sits below its ceiling, a clean dead-code analysis, and a production bundler for the shipped artifact.
5.0 / 510 of 10 weighted points earned — snapshot of 2026-08-04
strict-tsweight 2 ptsearned 2 / 2
Measures: TypeScript strict mode
Why this weight: The compiler’s strongest correctness net — it eliminates whole bug classes at build time rather than flagging them for later.
zero-lint-errorsweight 2 ptsearned 2 / 2
Measures: eslint reports no errors
Why this weight: Lint errors are defects the project has already agreed to prohibit; any nonzero count means the agreement is not being kept.
few-lint-warningsweight 3 ptsearned 3 / 3
Measures: eslint warnings vs a 200 ceiling
Why this weight: The live debt gauge of the dimension: unlike the binary checks it has range, moves with every edit, and rewards paying debt down — so it carries the most weight.
knip-cleanweight 2 ptsearned 2 / 2
Measures: no unused files/exports/deps (knip exits 0)
Why this weight: Dead code is untested, misleading surface area that still costs review and maintenance; keeping it at zero is a real, enforced discipline.
bundledweight 1 ptearned 1 / 1
Measures: a production bundler is configured
Why this weight: Matters for what ships, but it is mostly a one-time setup rather than an ongoing practice — hence the smallest weight.