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

webunpack.js

v0.0.2

Published

> A recon tool for security purposes > Find the modules packed (bundles) with webpack.js

Downloads

3

Readme

webunpack

A recon tool for security purposes
Find the modules packed (bundles) with webpack.js


Installation

Install globally webpack and webpack-cli:

npm install --global webpack
npm install --global webpack-cli

CLI example

Download the latest release of webunpack.
To display the help:

node webpack.js

To fetch the list of vulnerable npm modules:

node webunpack.js getvulns > vulnerablemodules.txt

To create a signatures database from vulnerable npm modules:
(warning: creation of database could take several days it is recommended to use precomputed database in dbs folder)

node webunpack.js createdb vulnerablemodules.txt ./dbs/signaturesdb.json

To update a signatures database from vulnerable npm modules:

node webunpack.js updatedb vulnerablemodules.txt ./dbs/signaturesdb.json

To filter signatures/remove duplicate signatures shared between modules:

cp ./dbs/signaturesdb.json ./dbs/signaturesdbfiltered.json
node webunpack.js filterdb vulnerablemodules.txt ./dbs/signaturesdbfiltered.json

To retrieve vulnerable npm modules from a packed file:

node webunpack.js unpack ./dbs/signaturesdbfiltered.json ./tests/testhandlebarsvuln/dist/main.js

API example

Update your package.json to use webunpack:

{
  "name": "test",
  "version": "0.0.1",
  "license": "MIT",
  "dependencies": {
    "webunpack.js": "^0.0.2"
  }
}

Unpack a file with unpackFile method:

var webunpack = require("webunpack.js"); 

var results = webunpack.unpackFile("./tests/testhandlebarsvuln/dist/main.js", "./dbs/signaturesdbfiltered.json");

console.dir(results);

The output should be the list of vulnerable modules identified in the packed file:

[ { name: 'handlebars',
    version: '4.3.2',
    vulnerable: 'https://npmjs.com/advisories/1325' },
  { name: 'handlebars',
    version: '4.4.1',
    vulnerable: 'https://npmjs.com/advisories/1325' },
  { name: 'handlebars',
    version: '4.2.2',
    vulnerable: 'https://npmjs.com/advisories/1164' } ]

API documentation


  • webunpack.unpackFile(packedfile, signaturesdb, mostrelevantmodule = false);
  • webunpack.unpackString(packedstring, signaturesdb, mostrelevantmodule = false);
    the last parameter if set to true imply that only the most relevant vulnerable module will be displayed.
  • webunpack.fetchVulnerabilities();
  • webunpack.createSignatures(vulnerablemodulesfile, signaturesdb);
  • webunpack.updateSignatures(vulnerablemodulesfile, signaturesdb);
  • webunpack.signaturesdbFilter(signaturesdb);

How it works?

For the moment the only source of npm vulnerable modules is https://npmjs.com/advisories/
For each vulnerable version of a module, createSignatures() method will compute a hash of each function.
Then unpackFile() method will compute the hash of each of the function inside a packed file and compare it to the ones in a signatures database.

Faq

Here