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

bawabu

v0.1.1

Published

A gatekeeper between AI coding agents and the packages they install.

Readme

bawabu

The gatekeeper between AI coding agents and the packages they install.

When an AI coding agent (Muse Code) runs npm install, Bawabu stops the install, checks the package, and lets it in only when it finds no evidence of harm. Most packages are cleared in about a second. Suspicious ones are run in a locked cloud sandbox baited with fake secrets and investigated by Muse Spark, which reads the code, decodes what's hidden, re-runs the sandbox under the conditions the malware is waiting for, and has to quote its evidence, which Bawabu checks against what the tools saw.

Full story, results and design: github.com/Amoh-Ntim/bawabu

Install

npm i -g bawabu        # Node.js 20+; no runtime dependencies

Check a package from the terminal

bawabu scan react-datepickr     # a name an AI made up: blocked, "did you mean react-datepicker?"
bawabu scan left-pad            # an established package: allowed in about a second

It prints the verdict, the evidence and a link to the report page. Exit code: 0 allowed, 1 blocked, 2 a human should decide (or the check failed).

Protect a Muse Code project

cd your-project
bawabu init                     # installs the Muse Code hook and .muse/bawabu.json

Then open the project in Muse Code and trust the workspace. The installs the agent runs (npm, npx, pnpm, yarn, bun, pip, uv, pipx, including ones hidden in scripts, whole-project installs with their direct dependencies, and new MCP servers) are checked first; installs it can't see into are blocked. The agent gets the verdict with the evidence, and is told not to try another way. It protects a well-meaning agent from bad packages; it isn't a sandbox around a hostile one (see Limits).

Use your own API key

By default the CLI uses the hosted demo service. To run everything on your own machine with your own Meta Model API key, including a built-in test lab of harmless practice attacks:

git clone https://github.com/Amoh-Ntim/bawabu.git && cd bawabu && uv sync
export META_API_KEY=...
uv run service/run_local.py

bawabu scan ci-build-cache-helper --local --lab    # a practice attack: Muse Spark investigates
bawabu demo                                        # a project for Muse Code, wired to your local service

See Try it with your own API key.

Commands

| Command | What it does | |---|---| | bawabu init [dir] [--local \| --service <url>] [--open-weights] [--force] | Install the hook and settings in a project, test the hook the way Muse runs it, and check the service answers | | bawabu scan <pkg>[@version] [--local] [--lab] [--open-weights] | Check one package and print the verdict and evidence | | bawabu demo [dir] | Create a project for trying Bawabu in Muse Code with the local service | | bawabu explain "<command>" | Show which installs Bawabu sees in a shell command | | bawabu check | Run by the hook (reads Muse's hook input on stdin) |

Privacy and safety

  • Only package names, versions and the registry's address leave your machine: never the command line, your code, your files, or credentials from .npmrc.
  • It fails closed: if the service can't be reached or a check takes too long, the install is blocked, not waved through.
  • Its settings live in .muse/, which the agent can't change without your approval.

The hosted service is a hackathon deployment: it may be slow, rate-limited or switched off later.

License

MIT. Built for the Meta Global AI Developer Hackathon (Indie track) by Samuel Amoh Ntim.