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

@cyberhub/trust-rc

v1.0.61

Published

Security Trust Report: [email protected] — 54/100 (C, standard). Security incident detected. Maintainer risk, supply chain analysis from 8 security databases.

Readme

Security Trust Report: rc

[email protected]: 54/100 | Grade: C | Tier: STANDARD (confidence: ±3)

Data verified on 2026-04-02 from 8 security databases.

TL;DR

  • Security incident detected — compromised via account takeover/sabotage
  • Pin your version and monitor for changes

⚠️ Security Incident Background

In November 2021, similar to coa, malicious versions were published through a compromised npm account.

Score Breakdown

Maintainer Trust:  █████████████░░░░░░░ 65/100
Package Health:    █████████████████░░░ 86/100
Supply Chain:      ██░░░░░░░░░░░░░░░░░░ 12/100
Community:         █████████░░░░░░░░░░░ 46/100

Why this score?

  • Supply Chain is 12 because: 1 security incident(s) in breach database, in breach database
  • Community is 46 because: no public GitHub repo linked (may be private or on another platform)

⚠️ Security Incident

This package was compromised via account takeover/sabotage (no CVE assigned). See Security Incident Background above for details.

Key Risk Flags

  • 🔴 CRITICAL: HISTORICAL BREACH: Malicious versions published via compromised maintainer (2021)
  • 🔴 CRITICAL: 1 CRITICAL security incident from breach database (no CVE assigned)
  • 🟠 HIGH: Primary maintainer account is less than 6 months old (0 days)

🛠️ What Should You Do?

Immediate:

  • 📌 Pin to known-safe version: 1.2.8 (before compromise)
  • 📖 Review the security incident above

Always: Pin version, run pkgtrust scan in CI, monitor at nrupak.com/trust/rc

Maintainers

Methodology: 18+ signals across 4 categories (Maintainer 35%, Package 25%, Supply Chain 25%, Community 15%). Full scoring docs →

Check your project: npm i -g @cyberhub/pkgtrust && pkgtrust scan rcCLI docs Data Sources: GitHub Advisories · OSV.dev · npm audit · Snyk · Socket.dev · npms.io · Bundlephobia · deps.dev


Report by pkgtrust · Dashboard · Compare · CLI

This is an automated security report. Not affiliated with the rc team. Updated 2026-04-02.