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

@jazzer.js/fuzzer

v4.0.0

Published

Jazzer.js libfuzzer-based fuzzer for Node.js

Downloads

9,509

Readme

@jazzer.js/fuzzer

This module provides a native Node.js addon which loads libfuzzer into Node.js. Users can install it with npm install, which tries to download a prebuilt shared object from GitHub but falls back to compilation on the user's machine if there is no suitable binary.

Loading the addon initializes libFuzzer and the sanitizer runtime. Users can then start the fuzzer with the exported startFuzzing or startFuzzingAsync functions; see the test for an example. In sync mode (--sync), the fuzzer runs on the main thread and blocks the event loop. In the default async mode, libFuzzer runs on a separate native thread and communicates with the JS event loop via a thread-safe function.

Development

The project can be built with npm run build (which is incremental after the first build); a subsequent npm test makes sure that the addon loads cleanly. Binaries can be prebuilt with npm run prebuild and uploaded with npm run prebuild -- --upload. Please format the code with clang-format (or use the format functionality of clangd).

Internally, the build system uses several steps:

  1. package.json defines the npm scripts.
  2. Several of them use prebuild or prebuild-install; together, those two tools implement a binary cache via GitHub releases, so that users don't have to build the code themselves.
  3. We run prebuild with the cmake-js backend, which makes it call cmake-js to build the code when necessary.
  4. cmake-js is a wrapper around CMake; it expects CMake and the C++ toolchain to exist on the machine already.
  5. In our CMake configuration, we set up compiler-rt as an external project; CMake fetches and builds it before compiling our own code against it.

To debug build issues, it's often useful to start with a plain cmake-js compile or cmake-js recompile, which just invokes CMake with a few extra arguments that help it find the Node.js headers and such.

When working on the addon's C++ code, you may want to use a language server like clangd for IDE features. CMake is configured to emit a compile_commands.json file, so the language server should work after the first npm install.