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

headerless

v0.1.3

Published

Strips format-defining header fields from binary assets at build time. Bundler-agnostic core.

Readme

headerless

Strips format-defining header fields from binary assets at build time, and puts them back in memory at runtime.

Not encryption, not DRM — it raises the cost of extracting assets from a shipped app from unzip to reverse-engineer. Anything visible to the renderer stays visible to a determined attacker; that is by design.

⚠️ WIP — API is not stable and this package is not published yet.

How it works

The cut fragment must be the key that reconstitutes the file. That single rule drives everything else:

  • A fixed-length cut is rejected. PNG signatures and JPEG SOI/APP0 are identical across files, so a restorer just writes the constant back.
  • Cuts are per format and target the fields that vary per file: PNG IHDR data and CRC, the WebP frame header, JPEG SOF0.
  • Constant runs are removed from the file but not stored in the fragment — they are regenerated on restore.
  • Formats without a parser fail loudly instead of falling back to a fixed cut.

Because the fragment is a per-file key rather than a shared constant, publishing the algorithm does not weaken it (Kerckhoffs). Only the fragments are secret.

Status

| | | | --- | --- | | detect() | done | | locate() / strip() / restore() | not implemented |

The design rationale is documented in the repository README.

License

MIT