Dependency Time Bomb
Parse common dependency manifests and flag unpinned, pre-release, and pre-1.0 version signals.
Dependency Health reviews the dependency surface of a repository: how many direct dependencies there are, how heavy the tree is, and where risk concentrates.
- users onboarded
- 640+
- doc modules generated
- 18k+
- files indexed
- 2.1M+
- avg to first docs
- ~2 min
What does Dependency Time Bomb check?
- Manifest and lockfile contents across the repository
- Direct dependency count per package and per workspace
- Heavy or duplicated packages and obvious overlap between libraries
- Outdated major versions and unpinned ranges that make builds drift
How does Dependency Time Bomb work?
- 1.Paste a public repository URL.
- 2.ShipDocs reads the manifests and lockfiles it finds.
- 3.You get a dependency report with the risky parts called out.
What do you get from Dependency Time Bomb?
- • A dependency count you can act on, per package
- • The packages most likely to cause upgrade pain
- • A shortlist of removals or consolidations worth doing
“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
Which package managers are supported?
- npm, pnpm, yarn, and bun lockfiles, plus Python, Go, Rust, PHP, and Ruby manifests when they are present.
Does it perform a security audit?
- It reports dependency structure and version drift. Vulnerability feeds come from your own tooling (npm audit, Dependabot, Snyk).
Why does dependency size matter?
- Every direct dependency is a long-term maintenance and security liability, and it slows down installed size and CI.
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.
- 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.
- 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