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

shai-hulud-checker

v0.2.1

Published

Scan yarn/npm/pnpm lockfiles for compromised packages from the Shai-Hulud npm supply-chain attack.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

sdlazarosdlazaro

Keywords

Readme

Mini Shai Hulud Checker - 2026-05-19 attack wave

Usage

  • Clone this repo
  • Go to the root folder where you have all your repos
  • Run node shai-hulud-checker/cli.mjs and wait a bit

Previous attacks

List of compromised packages for previous waves are distributed with the checker:

Each CSV has two columns:

Package,Malicious Versions
@scope/name,"1.0.1, 1.0.2, 1.0.3"
some-pkg,2.3.4

By default the checker uses the most recent wave. To check against a specific one, pass its date:

node shai-hulud-checker/cli.mjs --date 2026-05-19

You can also point at an arbitrary CSV anywhere on disk with --list path/to/file.csv.

Reading the output

By default, the report includes two groups: HITS (an installed version matches a compromised release) and PRESENCE (the package is on the list but at a version that wasn't flagged). To report only actual compromises, pass --hits-only:

node shai-hulud-checker/cli.mjs --hits-only

What to do if I'm hit? 2026-05-19

  • Read https://safedep.io/mini-shai-hulud-strikes-again-314-npm-packages-compromised/ carefully
  • Close and then clean up all IDEs and ADEs
  • Clean up your OS as it is compromised too
  • Clean up all your local Git repos
  • Check on GitHub whether any local repo had commits made to propagate the infection
  • Warn any contributors to any repos you have checked out on your machine

What to do if I'm hit? 2026-08-04

Read https://safedep.io/keyv-npm-supply-chain-compromise/ carefully. It contains remediation steps.

What to do if I'm using compromised packages but I'm not hit (I'm using older versions)?

Warn any contributors to these repos, as they might have updated local dependencies and might have gotten infected.