THC LEADERBOARD
Truth · Hardening · Clarity
Sign in with GitHub

Methodology folder page

THC Methodology

Truth, Hardening, and Clarity are evidence categories. The public level is computed from score, then constrained by deterministic caps.

Scorecard

1. Score Categories

The base score is built from four documented evidence categories.

Truth / 30

Strong

Explicit claims, public source of truth, boundaries, assumptions, and evidence trail.

Hardening / 35

Strong

Validation commands, tests, CI, failure modes, environment notes, and guardrails.

Clarity / 25

Improve

Fresh-clone setup, contributor guidance, operator docs, recovery notes, and navigation.

Audit History / 10

Improve

Changelog, decisions, known risks, uncertainty, and prior review trail.

2. Level Mapping

The score maps to a THC level before cap logic is applied.

THC-0 Unverified

Absent

Insufficient public evidence or major trust gaps remain.

THC-1 Documented

Improve

The repo explains itself, but hardening evidence may still be thin.

THC-2 Hardened

Improve

Validation and operational guardrails are visible enough to score.

THC-3 Inspectable

Strong

A reviewer can follow the repo, evidence, and decisions from public state.

THC-4 Reproducible

Strong

Setup and checks are strong enough for repeatable public review.

THC-5 High-THC

Strong

High score plus no unresolved cap blockers under the methodology.

3. Cap Checks

Caps lower the recommended level when evidence is missing, stale, private, or unverifiable.

Missing setup path

Absent

Caps level because reviewers cannot reproduce basic orientation.

No visible validation

Absent

Caps level when tests/CI/commands are absent or unverifiable.

Stale local artifacts

Improve

Local THC files point at a different revision than public review.

Private-only proof

Improve

Private dashboards or maintainer memory cannot earn public score credit.

Evidence Color Key

StrongGood public evidence.
ImprovePartial, stale, or needs tightening.
AbsentMissing, private, unverifiable, or unsafe to credit.
× Score is not certificationAbsent

Reports are review artifacts only. They are not security approval, production readiness, endorsement, or a reliability guarantee.

△ Caps are deterministicImprove

Missing setup, missing validation, stale artifacts, or unverifiable claims can cap the public level after scoring.

× Popularity does not countAbsent

Stars, maintainer reputation, package size, polish, or brand awareness do not increase THC score.

✓ Strong public evidence compoundsStrong

The best reports show a clean trail from claim, to file, to command, to decision history, all at the reviewed commit.