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

@afterpack/protection-map

v0.2.2

Published

AfterPack Protection Map viewer: render protection data into a self-contained HTML report

Readme

@afterpack/protection-map

The viewer for the AfterPack Protection Map: a single HTML file that shows your original source, shaded by how much transformation each part went through, with the weak spots a build left readable.

You usually do not need to install this package. The AfterPack CLI and every AfterPack plugin already use it to write .afterpack/protectionMap.html when your build has source maps. Open that file in a browser. It works offline, straight from disk. Two options control it: protectionMap.enabled turns it on or off, and protectionMap.detailed set to false leaves out the per-region list of transformations for a smaller file.

The Protection Map contains your original source. Keep it local: never deploy, publish or commit it. AfterPack tools write it under .afterpack/, which carries its own .gitignore and self-ignores.

Render one yourself

If you have Protection Map data as JSON, render it with the bundled command. The template ships with the package:

npx afterpack-protection-map report.json protection-map.html

Add --no-lineage for a smaller file without the per-region transform history.

Or from Node:

import { writeFileSync } from "node:fs";
import { renderProtectionMapHtml } from "@afterpack/protection-map";

const { html } = renderProtectionMapHtml(data);
writeFileSync("protection-map.html", html);

renderProtectionMapHtml(data, { template, includeLineage }) uses the bundled template unless you pass one, and includes lineage unless includeLineage is false.

Links

License

Apache-2.0.

Feedback

Questions, suggestions and bug reports: afterpack.dev/contact. You can also file a bug on GitHub Issues.