wrapped.dev is live · free · last verified 24 Oct 2026 · viability monitor
wrapped.dev
Turn a public GitHub repo into a free AI-written year-in-review built from its full commit history
As a free, no-account community artifact, wrapped.dev is a genuinely fun thing to point at your open-source repo — the Popular and Latest feeds let you see a finished wrap before running one, and the bot/high-activity flags show the team thought about what makes a commit graph misleading. Judge it as a shareable story, not analytics: it reads public repos only, the AI narrative can contain errors, the model runs are described by the project itself as expensive, and there's no per-developer breakdown and no collaboration layer. If you want ongoing monitoring, go to GitHub Insights; if you want to post a year-in-review to your community, wrapped.dev is the lighter, weirder option. Check that
Verdict generatedVerified 20d ago · liveness 54/100 · cite: rightaichoice.com/tools/wrapped-dev
- Open-source maintainers wanting a shareable year-in-review for a public repo
- Contributors to public repos who want their work surfaced in a narrative
- Community managers looking for a lightweight recap to post
- Hobbyists exploring AI-generated storytelling from code history
- Anyone who needs private repository analysis
- Teams needing ongoing monitoring or enterprise-grade analytics
- Managers who need per-developer contribution breakdowns
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip wrapped.dev if you need private-repo coverage, per-developer contribution numbers, or a report you can cite as fact — it wraps public repos only, in AI-written prose the team itself says may contain errors.
Wrapping a repository means cloning it and pushing the full commit history through large-context models, which the project describes as expensive — that's why it stays a free experiment with no promised uptime.
A standalone free tool rather than a tier in a pricing ladder, so there's nothing to upgrade to and no seat maths. Compare it with paid engineering-analytics platforms that charge per contributor per month for ongoing repository monitoring — wrapped.dev does one narrative artifact for $0 instead, with public-repo-only scope and no guaranteed uptime.
In short
wrapped.dev — Turn a public GitHub repo into a free AI-written year-in-review built from its full commit history. Best for Open-source maintainers wanting a shareable year-in-review for a public repo, Contributors to public repos who want their work surfaced in a narrative, Community managers looking for a lightweight recap to post. Free to use.
What is wrapped.dev?
wrapped.dev — Turn a public GitHub repo into a free AI-written year-in-review built from its full commit history. Best for Open-source maintainers wanting a shareable year-in-review for a public repo, Contributors to public repos who want their work surfaced in a narrative, Community managers looking for a lightweight recap to post. Free to use.
Paste a public GitHub repository URL and wrapped.dev clones it, walks the file changes in every commit, and sends the whole history through large-context models to return an AI-written year-in-review for the project. The output is a narrative summary rather than a commit-count chart: it highlights commit and contributor counts, detects trends across the year, and flags bot or high-activity surges so an automated commit stampede isn't read as human effort. Two browse feeds — Popular (repos other people have wrapped) and Latest (recently added) — let you see a finished wrap before running your own. It's aimed at open-source maintainers who want something shareable for their community and contributors who want their work surfaced in prose, and the team (@etbyrd and @hellovai) frames it as a hobby build rather than an audit tool. Positioning is deliberately different from GitHub Insights or Datadog: those are monitoring layers you check on a schedule, while wrapped.dev is a one-off community artifact you generate, post, and move on from. Crucially, the site is currently returning a 503 DEPLOYMENT_PAUSED page from Vercel, so treat availability as intermittent and confirm the site is live before you plan a post around it.
Key features
- Year-in-review wrap page generated from any public GitHub repository URL
- AI-written narrative summary of a repository's activity, not a commit-count chart
- Processes the file changes in every commit it analyzes
- Clones the repo and one-shots the full commit history through large-context models
- Commit and contributor count stat highlights
- Trend detection and insights across the year
- Bot and high-activity detection to flag automated commit surges
- Shareable wrap page for social media or a README
- Popular feed of repos other people have wrapped
- Latest feed of recently added repos
- No sign-up or account required
- Free to use
- Public repositories only
Behind the verdict
The interesting design choice here is that wrapped.dev treats "year in review" as a narrative problem rather than a charting problem. It clones the repository, processes the file changes in each commit, and one-shots the entire history through large-context models — the project names Gemini 1.5 Pro and Llama 3.3 70B via AWS Bedrock — to produce prose about what the repository actually did. That's a different artifact from a GitHub Insights graph, and the team says so explicitly: wrapped.dev is something you generate once, post, and move on from, not a monitoring layer. Strengths: the zero-friction entry point (type a URL, no account, no sign-up) is why it gets passed around; the Popular and Latest feeds give you examples before you risk a run; and the bot/high-activity detection is a real editorial touch — automated commit surges are exactly what makes repository activity stats lie, and the wraps call them out. Weaknesses are structural rather than fixable bugs. Public repositories only, so no private or internal project gets wrapped. The AI narrative can be wrong, which the team acknowledges and which matters if a contributor's work is described inaccurately. There is no per-developer breakdown and no team or multi-user access, so this can't do duty as an engineering-management report. And because the approach — cloning every repo and pushing whole histories through big-context models — is expensive, it runs as a free experiment rather than a supported service, which is consistent with what you see today: the Vercel deployment is paused and the site returns 503. Where it fits: a maintainer of a public open-source project who wants a shareable recap for a README or a social post, or a community manager looking for a lightweight seasonal artifact. Where it doesn't: any team that needs recurring reporting, private-repo coverage, per-person contribution accounting, or an authoritative record of what happened. For those, use GitHub's own Insights, or read the git log — wrapped.dev is a story about the year, not the year's audit trail. If you're considering it, check the site first, and treat the output as a draft to edit rather than a report to publish unread.
Models under the hood
as of 2026-10-16
Limitations
- Only public GitHub repositories are analyzed — private repos are out of scope entirely.
- It is a hobby project built by two developers, and the vendor states the AI-generated summaries may include errors, so treat the narrative as a starting point rather than a verified report.
- Each repo is cloned to gather data and the summary is produced by one-shotting the whole repository through large-context models, an approach the project itself describes as expensive — which is why it runs as a free experiment rather than a supported service.
- There is no per-developer breakdown, no team collaboration or multi-user access, and no ongoing monitoring layer.
- Availability is not guaranteed: as of this refresh the site returns a Vercel 503 DEPLOYMENT_PAUSED page, so check that it's live before planning a post.
as of 2026-10-24
Researching wrapped.dev? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Is wrapped.dev still active?
wrapped.dev is live · free · last verified 24 Oct 2026 · viability monitor.
Viability score
How well maintained and how widely used is wrapped.dev? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: November 2026
How we score →What do users say about wrapped.dev?
What people actually say about wrapped.dev — is it worth it?
We ran a structured research pass across product reviews, community discussions, and post-purchase forum threads to surface the patterns vendors won't publish themselves. Below: the recurring strengths, the hidden costs people mention most, and the cohort that consistently regrets adopting this tool.
ResearchedDiscussed by users across 2 sources (YouTube, Product Hunt) · researched Oct 21, 2026.
Weighted by the 21 posts each of 2 sources contributed.
- +Zero sign-up — paste a repo URL and get a result in one step
- +AI narrative tells the story behind commits, not just a count chart
- +Bot and high-activity flags stop automated commit surges reading as human effort
- +Free to use with no account, billing, or trial friction whatsoever
- +Genuinely celebrates open-source contributors in a way GitHub Insights doesn't
- −Only works on public repositories — private and internal repos are excluded entirely
- −AI summaries can be inaccurate; team calls it a hobby project, not an audit
- −No video or downloadable export, which users specifically requested for cross-platform sharing
- −Wants deeper contributor-level insights and personalized recommendations, currently missing
- −No account or history — you can't save, revisit, or track wraps over time
- • None — it's free; the real cost is the limitation to public repos and no support SLA
How we verified this
Every listed fact about wrapped.dev — pricing, features, links, status — is re-read from the vendor's own pages by our verification pipeline and each change is logged with a date; the last pass ran on 24 Oct 2026. Analysis is drafted with AI models and checked against our editorial standards before publishing; see how we verify.
Verification history
We have re-verified wrapped.dev 10 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — changed domain expiry
- — changed SSL certificate
- — changed who should skip it, limitations, our verdict, summary, pricing fit, use cases, setup time, who it suits, features, switching out, description, switching in, hidden costs
- — changed features, pricing tiers, our verdict, description, summary
- — changed integrations, description, pricing tiers, features, who it suits, who should skip it, our verdict, summary
- — changed our verdict, who it suits, description, features, hidden costs, limitations, switching in, switching out, who should skip it, pricing tiers, pricing fit, setup time, summary, use cases
Showing the 6 most recent of 10 verification passes.
Free to cite with attribution — this page re-verifies continuously.
How much does wrapped.dev cost in 2026?
wrapped.dev: Free to use. Pricing last verified 24 Oct 2026.
Plans compared
Every published wrapped.dev tier, its price as the vendor publishes it, who it fits, and what it adds over the tier below. The 12-month cost projection follows.
| Plan | Price | Billing | Who it's for |
|---|---|---|---|
| Free | Free | — | Maintainers of public open-source repos and community managers who want a one-off shareable recap without an account or a budget line.Adds: Starting tier — the only tier: a year-in-review wrap page for any public GitHub repo, with AI narrative, stat highlights, trend detection, bot flags and no sign-up required. |
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Where the pricing makes sense
The company stage and team size where wrapped.dev's pricing actually pencils out — and where peers do it cheaper.
A standalone free tool rather than a tier in a pricing ladder, so there's nothing to upgrade to and no seat maths. Compare it with paid engineering-analytics platforms that charge per contributor per month for ongoing repository monitoring — wrapped.dev does one narrative artifact for $0 instead, with public-repo-only scope and no guaranteed uptime.
Has wrapped.dev's pricing changed?
No plan price for wrapped.dev has moved since we began logging in Aug 2026; the pricing page is re-read on every verification pass.
Who should pick wrapped.dev?
Pick wrapped.dev if you are Open-source maintainers wanting a shareable year-in-review for a public repo, Contributors to public repos who want their work surfaced in a narrative, Community managers looking for a lightweight recap to post, Hobbyists exploring AI-generated storytelling from code history.
Look elsewhere if you are Anyone who needs private repository analysis, Teams needing ongoing monitoring or enterprise-grade analytics, Managers who need per-developer contribution breakdowns, Teams requiring collaboration or multi-user access features.
Skip it if Skip wrapped.dev if you need private-repo coverage, per-developer contribution numbers, or a report you can cite as fact — it wraps public repos only, in AI-written prose the team itself says may contain errors.
GeneratedReal-world workflow fit
Concrete scenarios for the personas wrapped.dev actually fits — and what changes day-one when you adopt it.
You paste your public repo URL into wrapped.dev, it clones the repo and processes the year's commits, and returns a wrap page with commit and contributor totals plus a written narrative of what the project did.
Outcome: You post the finished wrap page to social media or drop the link in your README, giving contributors a shareable recap without writing it yourself.
Before running anything on your own project, you open the Popular feed to look at wraps other people generated, then run your own repo and read the bot/high-activity flags.
Outcome: You know what a finished wrap looks like and can tell which activity spikes in your own project were automation rather than human contributions, so the recap you post is honest.
You check a public repo whose evolution you're curious about by wrapping it, reading the trend detection and stat highlights alongside the AI narrative.
Outcome: You get a high-level story of how the project changed over the year without reading raw git logs, and you treat the prose as a starting point rather than a verified record.
Use cases
- Generate a year-in-review wrap for your open-source repo to post on social media
- Summarize a repo's activity for the year without reading raw git logs
- Browse the Popular feed to see what happened in well-known repos over the past year
- Surface contributor impact by sharing a repo's AI-written recap with your community
- Get a high-level narrative of how a project evolved across the year
- Compare the year's story across several public repos you follow
Setup time & first value
How long it actually takes to get something useful out of wrapped.dev — broken out by persona, not the marketing-page minute.
Paste-a-URL fast: there is no account and no sign-up, so the only real step is submitting a public repo URL and waiting for the clone-and-summarize run to finish. Budget a few minutes per repo, and check first that the site isn't showing a paused deployment.
Switching to or from wrapped.dev
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From GitHub Insights: keep Insights for scheduled monitoring and use wrapped.dev only for the shareable narrative artifact you post once a year.
- →From reading raw git logs: submit the public repo URL and use the AI narrative plus stat highlights as a first pass, then spot-check the commits that matter.
- →From hand-written annual recaps: run the wrap page first, then edit the generated prose so you aren't starting from a blank page.
- ↗To GitHub Insights: move to repository traffic, commit activity and contributor graphs when you need ongoing monitoring rather than a one-off story.
- ↗To a paid engineering-analytics platform: go there when you need per-developer breakdowns, private repo coverage or a report you can audit.
- ↗To a hand-written recap: take the wrap page's commit and contributor counts as a starting reference and rewrite the narrative yourself if accuracy matters.
Integrations
Resources & guides
Tutorials & Learning
YouTube returned 6 videos for “wrapped.dev”, and we withheld 6: 6 did not mention wrapped.dev. We are showing none, because we could not prove any of them are about wrapped.dev.
Official links
What are the best wrapped.dev alternatives?
The closest alternatives to wrapped.dev we list are Sourcebot, GitDiagram and GitHub Copilot. Ranked by direct product-type match, not category overlap.
| Alternative | Pricing | Starts at | Last verified |
|---|---|---|---|
| Sourcebot | Freemium | Pricing not published | — |
| GitDiagram | Free | Free | — |
| GitHub Copilot | Freemium | Pricing not published | — |
Alternatives to wrapped.dev
View all
Sourcebot
Self-hosted code search and AI code Q&A that gives coding agents context across every repo you own
GitDiagram
GitDiagram turns any GitHub repository into an interactive file-structure diagram or a one-minute explainer video.
GitHub Copilot
GitHub Copilot is an AI coding agent that starts work from the issue or pull request already in your repo.
Tools that pair well with wrapped.dev
Common stack mates teams adopt alongside wrapped.dev, with the specific reason each pairing earns its keep.
Sourcebot
Self-hosted code search and AI code Q&A that gives coding agents context across every repo you own
GitDiagram
GitDiagram turns any GitHub repository into an interactive file-structure diagram or a one-minute explainer video.
GitHub Copilot
GitHub Copilot is an AI coding agent that starts work from the issue or pull request already in your repo.
wrapped.dev vs its closest rival
wrapped.dev's closest head-to-head is with Screenplayiq.
Our wrapped.dev vs Screenplayiq verdict written Jul 3, 2026 is more than 90 days old, so it is being re-reviewed against current data and is not shown.
Frequently asked questions
Categories
Best-of guides
For makers of wrapped.dev
- Get a Verified Listing for wrapped.dev ($39): a written decision within 1 working day.
- Free listing for another tool: Free reviews are decided in order, within 3 weeks of the review starting.
Used wrapped.dev? Help shape our editorial sentiment research.