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

event-metrics-q3x7

v1.0.8

Published

Authorized security-research probe (GitHub Bug Bounty, npm in scope). Contact [email protected].

Readme

@ncurran/sandbox-recon-880538 — authorized npm-sandbox security research

This is a benign package published under the author's own @ncurran scope as part of an authorized HackerOne / GitHub Bug Bounty engagement (npm is in scope).

On install it inspects its own execution environment (OS/host fingerprint, environment-variable key names only, network interfaces) and checks whether well-known cloud metadata endpoints are reachable from where the install script runs. It reports only status codes, response lengths, and hashes — never any credential, token value, or third-party data. It performs no persistence, no lateral movement, and no destructive action.

Purpose: to evaluate whether npm's package-analysis sandbox isolates untrusted install scripts from cloud instance-metadata services. If you are a normal consumer who installed this by accident, it has done nothing harmful — please disregard.

Contact: [email protected]