What problem does it solve? Engineering teams lack a consistent, repeatable way to measure repository health across security, correctness, infrastructure, maintainability, documentation, and freshness, making it hard to prioritize debt remediation or compare multiple projects. ## Core Features & Use Cases - Six-Category Scoring: Scans for hardcoded secrets, dependency vulnerabilities, test coverage, CI/CD configuration, TODO/FIXME counts, README quality, and dependency staleness, scoring each category 0-10 against a defined rubric. - Sandboxed Runtime Verification: Builds and tests repositories inside Docker containers with memory, CPU, and network limits so untrusted code never runs on the host. - Portfolio and Diff Modes: Aggregates per-repo results into a PORTFOLIO-HEALTH.md comparison matrix and diffs against previous DEBT.md files to track improvement or regression over time. - Use Case: Before open-sourcing a project or applying for jobs, run a portfolio audit across all your GitHub repositories to find which ones have missing LICENSE files, failing tests, or exposed secrets, then follow the ROI-ordered fix plan. ## Quick Start Ask Claude to audit this repository with the technical-debt-auditor skill and generate a DEBT.md report in the repo root.
