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

wasmkit

v2.0.3

Published

WASM extension and instrumentation toolkit

Readme

kit

Extendable and modular analysis of wasm files. The general concept is to allow the creation of Formats to view and recompile wasm, and let those Formats rely on predefined lower level formats.

I.E given an emscripten wasm file, the user parses with the emsc format. The emsc format then requests and retrieves LLVM function scope information and Struct information from the llvm and struct_finder formats. These formats then use data from the Highlevel Web Assembly (hl_wasm) format which provides a high level IR for interacting with wasm. Then hl_wasm uses data from its lower level sibling wasm, which finally gets the most pure sections data from the raw format. All these formats compound together into the abstract emsc layer.

It will not stop at emsc, for ex unity could extend that. Contribution is welcome to create more advanced layers.

Exsample code:

const kit = wasmkit(wasm_file);

const raw = kit.raw();
const wasm = kit.wasm();
const llvm = kit.as(LLVMModule, { options }); // iirc this has changed a bit since this demo was written

if (LLVMModule.COMPILEABLE) {
    llvm.funcs[0].shadowStack.size += 4;

    llvm.compile();
}

TODO

Before this is fully doable, efforts must be focused on better struct finding algos (will need a Format that disassembles into an SSA view first). For this reason, we are currently at a somewhat unusable state besides basic wasm parsing.

Language Choice

We wanted something that would be easy for people to contribute to. We wanted something that could easily be integrated to Web as well as backend analysis.

Speed

The systems explained above parse 100% of the binary, which is slow especially given the fact we have written this in TypeScript. To enhance speed we will allow for selective parsing of only user-requested data, but there is also the possibility of off-thread parsing.

Maintainability

It could be a struggle to keep this up to date with the possible future wasm standards. For this reason it might be worth looking into using binaryen for the backend to the lower level layers.

License

Please see ./LICENSE