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

@localrepo/pledge

v1.0.0

Published

Use @localrepo/* for your monorepo package names

Readme

@localrepo/pledge

My name is Benjie Gillam; you can find me on Twitter, GitHub and npm as @benjie. I hereby pledge that I shall not publish any packages other than this package to the @localrepo scope on the npm registry.

Why?

The aim of this pledge it to make using @localrepo/* as the name of packages in your own monorepos a relatively safe thing to do (no risk of hijacking).

To npm employees:

I hereby grant you permission to remove any package within the @localrepo scope (i.e. packages named @localrepo/*) except for this @localrepo/pledge package without warning or confirmation.

How can I trust this?

  • Visit https://www.npmjs.com/org/localrepo and assert there's only one package
  • Visit https://github.com/benjie/localrepo-pledge and see this content
  • Visit https://github.com/sponsors/benjie for some social proof

How might this change in future?

I'm hoping that npm will make something like this official. If they want to do so using this namespace I'd certainly be happy to discuss it with them; that may result in this package disappearing and myself ceding control of the @localrepo scope to npm.

Keywords

To help people find this npm scope, here's some search terms they might use (also search terms I used to try and find an already existing scope like this):

  • safe npm scope for monorepo
  • npm organization for local package names
  • reserved npm namespace for monorepos
  • scope to avoid npm dependency hijacking
  • monorepo package naming