# Repo Complexity Score - ShipDocs

> A 0–100 complexity score for any public repo, with the actual signals behind it. Free, no signup.

**URL:** https://shipdocs.sh/tools/complexity

## What it produces

A single number from **0 (trivial)** to **100 (very complex)** plus the breakdown that produced it:

- **File count** and **total lines of code**.
- **Language mix** - which languages and what share of the codebase.
- **Dependency graph depth** - how deeply modules import each other.
- **Hottest files** - the longest files and the files most depended on.
- **Deepest paths** - directory nesting that signals architectural fragmentation.

## How the score is computed

The score is a weighted blend of:

- File and LOC totals (volume signal).
- Language diversity (polyglot repos rank higher).
- Dependency-graph fan-in / fan-out percentiles.
- Path-depth distribution.
- Outlier file-size ratio.

The breakdown is shown next to the score so you can see *why* it landed where it did, not just the number.

## Use cases

- **Sizing onboarding** - estimate how long a new hire will need to come up to speed.
- **Pre-acquisition / due diligence** - get a quick read on a target repo before deeper review.
- **OSS evaluation** - compare alternatives before adopting a library.
- **Refactor planning** - find the deepest paths and longest files to target first.

## Limits

- Public repos only.
- Heuristic, not a defect-prediction model. Use it as a signal, not a verdict.
- For per-component documentation and AI chat over your private code, use the full ShipDocs product: https://shipdocs.sh/.

## Pricing

Free. No signup, no credit card.