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

unreadme

v0.1.1

Published

The README you never wrote

Downloads

20

Readme

  ┌──────────────────────────────────┐
  │  unREADME                        │
  │  the README you never wrote.     │
  └──────────────────────────────────┘

npm version license node

Drop unreadme in any repo. It reads your source code and generates a professional README.md in seconds — powered by Claude.


Prerequisites


API key setup

unREADME needs your Anthropic API key to call Claude. Set it once and it works everywhere:

# Add to your shell profile (recommended — works in every directory)
echo 'export ANTHROPIC_API_KEY=your_key_here' >> ~/.zshrc
source ~/.zshrc

Alternatively, put it in a .env file inside the repo you're documenting:

echo 'ANTHROPIC_API_KEY=your_key_here' > .env

Never commit your API key. Make sure .env is in your .gitignore.


Installation

# No install — run directly with npx
npx unreadme

# Or install globally
npm install -g unreadme

Usage

# Generate README for the current directory
unreadme

# Generate README for a different repo
unreadme --dir ~/projects/my-app

# Preview the diff before writing
unreadme --preview

# Print to stdout only, don't write the file
unreadme --dry-run

# Skip if README.md already exists
unreadme --no-overwrite

# Change the writing style
unreadme --persona minimal      # shortest possible README
unreadme --persona opinionated  # confident, active voice
unreadme --persona standard     # default: professional and complete

How it works

  1. Scans your repo and picks the most informative files (respects a ~60k character token budget)
  2. Reads git metadata — branch, recent commits, remote URL, detected language
  3. Sends everything to Claude as structured context
  4. Streams the generated README back and writes it to README.md

Contributing

Issues and PRs welcome. Open an issue first for any significant changes.


License

MIT