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

@marcfargas/pi-safety

v0.1.1

Published

Safety classification registry for pi agent tool calls — glob-based READ/WRITE command matching

Readme

@marcfargas/pi-safety

Safety classification registry for pi agent tool calls.

Provides glob-based command pattern matching to classify bash commands as READ (safe, no side effects) or WRITE (requires approval/planning).

Usage

import { SafetyRegistry, globMatch } from "@marcfargas/pi-safety";

const registry = new SafetyRegistry();

// Register safety patterns from a skill
// Tool name is the CLI name; patterns can include runner prefixes (npx, node, etc.)
registry.register("go-gmail", {
  "npx go-gmail * search *": "READ",
  "npx go-gmail * get *": "READ",
  "npx go-gmail * send *": "WRITE",
  "npx go-gmail * draft *": "WRITE",
}, "WRITE");

// Resolve a command
registry.resolve("npx go-gmail [email protected] search 'invoice'");
// → "READ"

registry.resolve("npx go-gmail [email protected] send --to [email protected]");
// → "WRITE"

registry.resolve("curl https://example.com");
// → null (no matching registry entry)

Pattern Validation

Patterns must start with the tool name, optionally preceded by a runner prefix:

// ✅ Valid patterns for tool "go-gmail"
"go-gmail * search *"         // direct invocation
"npx go-gmail * search *"    // npx runner prefix

// ✅ Valid patterns for tool "gcloud"
"gcloud * list *"             // direct invocation

// ❌ Rejected patterns
"* search *"                  // wildcard before tool name
"search go-gmail"             // tool name not at start

Supported runner prefixes: npx, node, python, python3, deno, bun, ruby, java, dotnet.

API

SafetyRegistry

  • register(tool, commands, defaultLevel?) — Register command patterns for a tool
  • resolve(command) — Resolve a command to READ/WRITE/null
  • inspect() — List registered tools
  • inspectTool(tool) — Get patterns for a tool
  • size — Number of registered tools
  • clear() — Clear all entries

globMatch(pattern, command)

Match a glob pattern against a command string. * matches any sequence of characters.

Types

  • SafetyLevel"READ" | "WRITE"
  • SafetyEntry{ commands: Array<{pattern, level}>, default: SafetyLevel }