Calibrated, not guessed. Five engineering pillars, one score: See our MethodologySee our Methodology
Know if your codebase is actually in good shape, or just looks fine. One command, 30 seconds, nothing leaves your machine.
npx @sprinno/scan in your project directory. No sign-up, no config, no repo connection.
Security, architecture, testing, process maturity, and team dynamics — all scanned on your machine.
See exactly where you stand, what's dragging the score down, and how you compare to companies at your stage.
See exactly which components changed since your last scan, and how that moved your score.
Same graph, four lenses — Diligence, Investor, Signal Flow, or Blueprint.
Five deterministic chapters, generated straight from the scan. No AI hallucination, no guesswork.
Quality signals checked per scan
Run locally — no setup, no sign-up
See whether last sprint moved your score up or down, not just where it sits today.
Know if you're ahead of or behind teams at the same stage and sector, not just "good in the abstract.
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
A summary signal backed by five inspectable pillars — not a black box. Drill into what drives the score and what your team can improve.
Get a defensible number in 30 seconds instead of writing a check for a manual review.
Drop it straight into a pitch deck or board report; it already speaks their language.
Companies in our reference benchmark
Statistically calibrated, not opinion-based
Get one score you can defend — and five buckets underneath it, so anyone who asks "why?" gets a real answer, down to test coverage, linting, and CI health.
Never remember to run a scan again — it watches every push, every PR, on a schedule you set.
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 tells you, in one number, how your codebase actually stacks up — and shows you exactly what's dragging your score down. Think of it as the SAT score for your codebase.
Yes — the scanner is fully open-source: what we scan for, how we detect it, and the full list of metrics are all in the public repo. What's not public is how those metrics are weighted into your final score — that's calibrated from data across hundreds of repos and kept private, the same way a credit score's inputs are public but the formula isn't. Publish the weights and the score stops meaning anything — teams start optimizing for the formula instead of for actually shipping better code.
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) to combine open, publicly-documented metrics — test coverage, dependency freshness, architecture signals, and more — into one score. The metrics themselves aren't a secret; you can see all of them. What's proprietary is how heavily each one is weighted, calibrated empirically from real repo data and kept private for the same reason above. Your score is also contextual to your stage — what's good for a seed startup differs from a Series B company.
Yes — your code stays yours. Nothing runs on our servers, nothing gets uploaded. That also makes it safe to run during a fundraise or an audit, when you'd rather not hand your code to anyone.
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, team dynamics, and business alignment. 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. The metrics we check are public — you know exactly what's being measured. The weights that combine them into a score aren't, so you can't know which metric to juice for maximum points. And the metrics that matter most are ones requiring genuine engineering quality, not something you can fake.
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.
Company Score is a weighted, multi-repo quality score. Assign each repo a role — Core Backend, Core Frontend, CLI/SDK, Supporting Service, etc. — and Sprinno computes a single company-wide score with per-bucket breakdowns. It accounts for your funding stage and the relative importance of each repo to your business. Available on Pro and Team plans.
After a scan, run `sprinno fix` to auto-heal findings. The CLI detects your AI coding agent (Cursor, Copilot, Windsurf, etc.), triages findings by severity, generates fix branches, and verifies the score improved. Auto-fixable issues are free on all plans; needs-review fixes are unlimited on Pulse+.
After two or more scans on the same repo, Sprinno computes a graph delta — showing which components were added, removed, or changed, which findings were resolved or introduced, and how the score moved. It's the diff for your architecture, not just your code.
Sprinno badges are live-updating SVG images that show your quality score. Embed them in your README, landing page, or pitch deck with a single HTML snippet or Markdown line. Badges are available on Pulse plans and above, and include a verification link back to your Sprinno profile.
Yes. Pro and Team users can export scans as self-contained HTML reports, generate PDF receipts, and create shareable links. The canvas supports four visual presets (Diligence, Investor, Signal Flow, Blueprint), and you can walk through guided chapters for presenting to non-technical stakeholders.
See your whole company's engineering health in one score, not repo by repo — assign roles, weight by importance, get one number.
Know exactly what changed in your architecture since last time — compare graphs, switch views, walk the story.
Let Sprinno fix what it finds — auto-detects your AI agent, triages by severity, opens fix branches, confirms the score went up.
Prove your score without a screenshot — live badges for your README, HTML/PDF exports for anyone who needs the full report.
How we score engineering quality — the science behind the Diligence Score, from Latent Capability Scoring to peer calibration.
