Dead Code / Orphan Finder
Find files that have no matching import, require, or path reference elsewhere. Results are candidates, not proof.
Dead Code Finder looks for what the repository no longer needs: exports nothing imports, files nothing references, and duplicated helpers that drifted apart.
- users onboarded
- 640+
- doc modules generated
- 18k+
- files indexed
- 2.1M+
- avg to first docs
- ~2 min
What does Dead Code Finder check?
- Exported symbols with no inbound import anywhere in the tree
- Files that no other file imports or executes
- Duplicated helper functions in more than one module
- Feature flags and configuration keys that nothing reads
How does Dead Code Finder work?
- 1.Paste a public repository URL.
- 2.ShipDocs builds an import graph from the source files.
- 3.Candidates are ranked by how safe they look to delete.
What do you get from Dead Code Finder?
- • A candidate list of unused exports and files with paths
- • Confidence notes so you delete the safe ones first
- • A smaller surface to document afterwards
“I was spending 4 hours every sprint updating our internal documentation. ShipDocs indexed our monorepo in under 3 minutes, and the answers cite real files.”
Frequently asked questions
Is the result safe to delete blindly?
- No. Dynamic imports, reflection, and config-driven loading can hide usage, so treat the list as candidates and verify each one.
Does it analyse a monorepo?
- Yes. Cross-package imports inside the repository are part of the graph, so shared packages are not reported as unused.
How does this help documentation?
- Documenting dead code is wasted effort. Removing it first makes the docs smaller and more accurate.
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.
- 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.
- Repo Complexity Score — Cyclomatic complexity, nesting depth and the files that slow teams down.
All free developer tools · Live examples of generated documentation · How ShipDocs works
By The ShipDocs team · Reviewed