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

sbom-sanitizer

v1.0.0

Published

A simple tool to remove likely unneeded proprietary information from SBOMs

Downloads

3

Readme

sbom-sanitizer

This is a simple tool that sanitizes a CycloneDX SBOM by removing potentially sensitive information such as component names, filenames, paths, etc. It identifies the most common fields that may contain sensitive information and removes them.

Why?

SBOM (Software Bill of Material) files are an increasingly important way of being aware of your software stack as well as determining and proving the security status of your dependencies. SBOMs are often shared with third parties doing due diligence or security checks.

The problem is that SBOMs themselves can contain information you don't want to share about your internal systems, such as component names, file paths, etc. Most tools that process SBOMs only care about dependencies and versions.

Feedback

PRs and issues are welcome if it's not removing something you would like sanitized prior to sharing externally. We could add more options or sanitize data differently if it breaks compatibility with a tool.