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

@bugzapper/worker

v0.1.5

Published

Bugzapper Worker is a local component that enables Bugzapper AI agents to access your local resources, such as files on your local host.

Readme

Bugzapper Worker

Bugzapper Worker is a local component that enables Bugzapper AI agents to access your local resources, such as files on your local host.

Installation

System Requirements

  • Node.js version 20 or higher

Quick Start

Run instantly in your working directory without installation:

npx @bugzapper/worker

Global Installation

Install globally using npm:

npm install -g @bugzapper/worker

Once installed, navigate to the directory you want to grant Bugzapper agents access to and run:

bugzapper-worker

Architecture

MCP Servers

By default, Bugzapper Worker already provides basic tools for working with your local files. You can also extend the toolset by using external MCP servers.

To use external MCP servers, add their definitions into the ~/.bugzapper/settings.json file:

{
    "mcpServers": {
        "serverName": {
            "command": "path/to/server",
            "args": ["--arg1", "value1"],
            "env": {
                "API_KEY": "$MY_API_TOKEN"
            },
            "cwd": "./server-directory",
            "timeout": 30000,
            "trust": false
        }
    }
}

The configuration requires one of the following properties:

  • command (string): Path to the executable for Stdio transport
  • url (string): SSE endpoint URL (e.g., "http://localhost:8080/sse")
  • httpUrl (string): HTTP streaming endpoint URL

Sandboxing

You can execute Bugzapper Worker within a isolated environment to prevent potentially unsafe operations by using the --sandbox or -s flag:

bugzapper-worker --sandbox <sandbox-method>

Supported sandboxing methods: sandbox-exec (MacOS only), docker, podman.

The sandbox-exec method uses the lightweight MacOS Seatbelt with default profile permissive-open: restricts writes outside working directory but allows most other operations.

Your host needs to have Docker/Podman installed if you want to use to docker or podman sandboxing method. By default, Bugzapper Worker will use the pre-built bugzapper-worker/sandbox image. It will pull that image to your host on first use.