npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

you-wrapped

v0.3.1

Published

Turn the record your Mac already keeps into a portrait of your year. Runs entirely on your machine.

Downloads

49

Readme

you-wrapped

A portrait of your year, assembled from the record your Mac already keeps.

Not "you sent 40,000 texts 🎉". A real read: the one trait that explains most of your behavior, the trend you can't see from inside it, a dated day where two commitments collided, and the wins you've been discounting.

npx you-wrapped

Zero dependencies. Runs entirely on your machine.


What it reads

| Source | What it takes | |---|---| | iMessage | Your sent messages — language, rhythm, who you talk to | | Apple Notes | What you write to nobody; tasks you keep rewriting | | Contacts | Names, so numbers become people | | Chrome + Safari | Searches, split by desktop vs phone — they're different minds | | Photos | Metadata only. Dates and coordinates. No images are ever opened. |

Missing a source? It's skipped with a reason. Partial data still makes a portrait.

What it writes

you-wrapped-out/
  signals.json         aggregate counts and trends — no message content
  evidence.local.md    your own words, quoted — KEEP THIS PRIVATE
  prompt.md            paste into Claude if you don't want to use an API key
  portrait.json        the analysis          (with --synthesize)
  wrapped.html         your portrait         (with --synthesize)
  wrapped.share.html   redacted, safe to post

wrapped.html has two modes: swipeable story cards (arrows, tap, or swipe) and a
full long-read with every finding at length. Press R to switch.

Usage

npx you-wrapped                      # extract + analyze, write the prompt
npx you-wrapped --synthesize         # also call Claude (needs ANTHROPIC_API_KEY)
npx you-wrapped --days 400           # how far back to read
npx you-wrapped --render p.json      # re-render a portrait you already have

Without --synthesize, nothing touches the network at all. Open prompt.md, paste it into Claude or ChatGPT, save the JSON it returns, and run --render.

Privacy

This reads your life. The design follows from that.

  • Local by default. No telemetry, no analytics, no server. There is nothing to opt out of.
  • --synthesize is the only network call. It sends aggregate signals plus short quotes to Anthropic using your key. Nothing is stored by this tool.
  • Two outputs, two audiences. wrapped.html has your names in it. wrapped.share.html strips emails, phones, addresses, links, tokens, and every name harvested from your own contacts and chat titles, then replaces coordinates with city labels. Redaction is deny-by-default: it strips first, and only what survives gets rendered.
  • evidence.local.md is the sensitive file. It's named that way on purpose. Don't post it.

Read wrapped.share.html before you share it. It's your life; verify the scrub.

Requirements

macOS, Node 22.5+. Your terminal needs Full Disk Access: System Settings → Privacy & Security → Full Disk Access → add Terminal/iTerm.

Why the extraction is the hard part

Four things silently return wrong answers instead of errors, and every one of them took real debugging:

  1. ~44% of iMessages have text = NULL. The body lives in attributedBody, an NSKeyedArchiver typedstream blob. Skip it and you lose half the corpus with no error.
  2. Contacts aren't in the obvious database. AddressBook-v22.abcddb is near-empty; real records live in Sources/<UUID>/.
  3. Apple Notes bodies are gzipped protobuf — and inflating leaves binary framing between text runs that has to be filtered heuristically.
  4. Timestamps overflow. Messages stores nanoseconds since 2001, Chrome stores microseconds since 1601. Both exceed Number.MAX_SAFE_INTEGER, so the conversion has to happen inside SQLite.

License

MIT. Your data is yours; this tool never sees it.