One command. Real scores. See exactly how solid your engineering is — benchmarked against real companies at your stage. No sign-up required.
Quality signals checked per scan
Run locally — no setup, no sign-up
Every scan measures what matters
See where you stand vs. your cohort
OHLC — score movement per scan vs. peer range
Diligence Score
acme-corp
Jun 14, 2026
Companies in our reference benchmark
Statistically calibrated, not opinion-based
One score, five buckets. Each bucket breaks down into sub-metrics: test coverage, linting, CI pipelines, dependency freshness, and more.
Plugs into GitHub. Scans on every push, PR, and schedule.
Surfaces the single sharpest risk signal per scan. No noise, just what matters.
See where any repo ranks against peers at the same stage, sector, and team size. Percentile-based context, not arbitrary thresholds.
Everything you need to know about our open-source scanner and how we measure engineering quality.
Sprinno is an open-source code quality scanner that produces the first Latent Capability Scoring standard for measuring software engineering quality. Think of it as the SAT score for your codebase — an objective, reproducible measure of how well your team builds software.
Yes. The CLI scanner (@sprinno/scan) is fully open-source. Your code never leaves your machine — everything runs locally. The scanning engine, scoring logic, and quality ontology are all open. Sprinno Cloud (dashboards, percentiles, recommendations) is the paid product built on top.
Just run `npx @sprinno/scan` in your project directory. No sign-up, no repo connection, no config files. It runs locally in about 30 seconds and gives you a quality score across five engineering pillars. That's it.
We use Latent Capability Scoring (LCS) — our proprietary calibration algorithm that determines which metrics actually distinguish strong engineering from weak engineering. LCS assesses your code across five pillars — Code Health, Process Maturity, Architecture, Resilience, and Documentation — and empirically weights each metric based on its discrimination power. Your score is contextual to your stage — what's good for a seed startup differs from a Series B company.
Absolutely. The scanner runs entirely on your machine. We never see, store, or transmit your source code. Only anonymous quality scores (numbers, not code) are optionally sent to improve calibration for everyone. You can opt out of reporting entirely.
Developers and engineering teams who want an honest picture of their codebase quality. Run it to find your weak spots, track improvement over time, and benchmark against peers. Investors and due-diligence firms also use Sprinno Cloud for objective assessments during fundraises and M&A.
Static analysis tools check code against fixed rule thresholds — they're deterministic but shallow. Sprinno goes far beyond code-level checks: we assess process maturity, architecture quality, resilience, and documentation. Our weights are empirically derived from data across hundreds of repos, not arbitrary thresholds set by experts.
The open-source CLI gives you a quality score, pillar breakdown, and a .sprinno.json file — all locally. Sprinno Cloud adds historical trends, percentile comparisons against your cohort, full LCS-calibrated scores (more accurate than CLI), team dashboards, and AI-powered recommendations. The CLI is the foundation; Cloud is the upgrade.
Not easily. Weights are proprietary and empirically derived, so you can't know which metrics carry the most influence. More importantly, the metrics that discriminate are ones requiring genuine engineering quality — you can't fake meaningful test coverage or healthy architecture.
Metrics are stack-agnostic at the pillar level. Whether you write Python, TypeScript, Go, Rust, Java, or anything else, we measure the same underlying engineering behaviors. Stack-specific calibrations exist only for language-level metrics where normalization is needed.
