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

opensrc

v0.6.0

Published

Fetch source code for npm packages to give coding agents deeper context

Readme

opensrc

Fetch source code for npm packages to give coding agents deeper context than types alone.

Why?

When working with AI coding agents, types and documentation often aren't enough. Sometimes the agent needs to understand the implementation - how something works internally, not just its interface.

opensrc automates the process of fetching package source code so your agent can reference it when needed.

Installation

npm install -g opensrc

Or use with npx:

npx opensrc <package>

Usage

npm Packages

# Fetch source for a package (auto-detects version from lockfile)
opensrc zod

# Fetch specific version
opensrc [email protected]

# Fetch multiple packages
opensrc react react-dom next

Re-running opensrc <package> automatically updates to match your installed version—no flags needed.

GitHub Repositories

You can also fetch source code directly from any public GitHub repository:

# Using github: prefix
opensrc github:owner/repo

# Using owner/repo shorthand
opensrc facebook/react

# Using full GitHub URL
opensrc https://github.com/colinhacks/zod

# Fetch a specific branch or tag
opensrc owner/[email protected]
opensrc owner/repo#main

# Mix packages and repos
opensrc zod facebook/react

GitHub repos are stored as opensrc/owner--repo/.

Managing Sources

# List fetched sources
opensrc list

# Remove a source (package or repo)
opensrc remove zod
opensrc remove owner--repo

File Modifications

On first run, opensrc will ask for permission to modify these files:

  • .gitignore — adds opensrc/ to ignore list
  • tsconfig.json — excludes opensrc/ from compilation
  • AGENTS.md — adds a section pointing agents to the source code

Your choice is saved to opensrc/settings.json so you won't be prompted again.

To skip the prompt, use the --modify flag:

# Allow file modifications
opensrc zod --modify

# Deny file modifications
opensrc zod --modify=false

How it works

  1. Queries the npm registry to find the package's repository URL
  2. Detects the installed version from your lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock)
  3. Clones the repository at the matching git tag
  4. Stores the source in opensrc/<package-name>/
  5. If permitted: adds opensrc/ to .gitignore, excludes from tsconfig.json, updates AGENTS.md

Output

After running opensrc zod:

opensrc/
├── settings.json       # Your modification preferences
├── sources.json        # Index of fetched packages
└── zod/
    ├── src/
    ├── package.json
    └── ...

The sources.json file lists all fetched packages with their versions, so agents know what's available:

{
  "packages": [
    { "name": "zod", "version": "3.22.0", "path": "opensrc/zod" }
  ]
}

The settings.json file stores your preferences:

{
  "allowFileModifications": true
}

License

Apache-2.0