Repo Wrapped
A shareable snapshot of your repository: languages, size, dependency count, and personality tags.
Repo Wrapped is a shareable stats card for a public repository: languages, file counts, hotspots, and the size of the codebase in numbers you can post.
- users onboarded
- 640+
- doc modules generated
- 18k+
- files indexed
- 2.1M+
- avg to first docs
- ~2 min
What does Repo Wrapped check?
- Language mix by source bytes (GitHub Linguist when available, a local line-count pass otherwise)
- File and directory counts, largest files, and generated/vendored code
- Commit activity and the busiest directories over the last year
- Documentation status: which parts of the repo have no docs at all
How does Repo Wrapped work?
- 1.Paste a public GitHub, GitLab, or Bitbucket URL.
- 2.ShipDocs clones and scans the tree; nothing is written to your account.
- 3.The card renders on this page and can be downloaded as an image.
What do you get from Repo Wrapped?
- • A share-ready card with real numbers from the repo
- • A language and size breakdown you can put in a README or a launch post
- • A first read on which directories would need documentation first
“Every AI tool invented APIs we don't have. ShipDocs cited src/routes/billing.ts on the first question. That alone paid for Advanced.”
Frequently asked questions
Does Repo Wrapped need a ShipDocs account?
- No. Repo Wrapped works on a public repository URL and renders a card without signing up.
Which repositories work?
- Any public GitHub, GitLab, or Bitbucket repository. Private repos need a connected account inside the app.
Is the repository cloned or stored?
- The tool reads the tree to compute the stats. Nothing from the run is kept after the card is generated.
More free tools and examples
- 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.
- 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