Repo Complexity Score
How complex is this repo, really?
A 0–100 score with the actual signals behind it: file count, total lines, language mix, dependency graph, and the deepest paths and longest files in the project.
Want full structured docs for this repo? Generate them with ShipDocs.
Complexity Hotspots ranks the files in a repository by how hard they are to change: size, branching, nesting, and how many other files depend on them.
- users onboarded
- 640+
- doc modules generated
- 18k+
- files indexed
- 2.1M+
- avg to first docs
- ~2 min
What does Repo Complexity Score check?
- File length and function length outliers
- Conditional and loop density per function
- Nesting depth and early-return structure
- Inbound dependency count, which multiplies the cost of every change
How does Repo Complexity Score work?
- 1.Paste a public repository URL.
- 2.ShipDocs parses the source and computes per-file complexity signals.
- 3.Files are ranked so the top of the list is where refactoring pays off.
What do you get from Repo Complexity Score?
- • A ranked hotspot list with paths and reasons
- • The files that most deserve documentation before refactoring
- • A starting point for a technical-debt conversation
“CodeWiki couldn't touch our private repo. Same afternoon we had encrypted docs, a diagram, and chat with file paths. New hire onboarded in a day.”
Frequently asked questions
Which languages are analysed?
- The mainstream languages ShipDocs indexes: TypeScript, JavaScript, Python, Go, Rust, Java, Ruby, PHP, C/C++, and Kotlin.
Does a high score mean the code is bad?
- Not by itself. A large parser or state machine can be legitimately complex. The point is to know which files cost the most to change.
How should I use the list?
- Document the top hotspots first, then split the ones that keep changing. Complexity plus churn is the real signal.
More free tools and examples
- Repo Wrapped — Shareable stats card for any public repo: languages, hotspots, doc coverage.
- Onboarding Time Estimator — How long a new engineer needs to ship their first change in your repo.
- Docs Gap Map — Which files and modules have no documentation at all.
- Dependency Time Bomb — Outdated, unmaintained and risky dependencies, ranked by upgrade pain.
- Dead Code Finder — Unused files, exports and dependencies that can safely be deleted.
- Production Readiness Audit — Tests, CI, error handling, secrets and deployment hygiene in one report.
- Architecture Diagram — A Mermaid diagram of modules and their real import relationships.
- Agent-Readiness Score — Score any docs URL 0–100 for LLM and coding-agent consumption.
All free developer tools · Live examples of generated documentation · How ShipDocs works
By The ShipDocs team · Reviewed