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

pi-safety-path-protection

v0.1.1

Published

Protects sensitive paths (.env files, .git internals, node_modules, SSH keys) from unauthorized reads and writes across all tools — read, write, edit, and bash.

Downloads

194

Readme

🔒 Safety Guard: Path Protection

Protects sensitive directories and files from unauthorized access across all tool types (read, write, edit, and bash).

What it protects

🔴 Blocked — read & write

| Path | Why | |------|-----| | .git/ internals | Prevents repository corruption (loose objects, refs, config) |

🔴 Blocked — write only (read allowed)

| Path | Why | |------|-----| | node_modules/ | Managed by package managers — direct edits break lockfile integrity | | .env, .env.local, .env.production, .env.* | Secrets files — agent must never modify credentials |

🟡 Confirmation required — write only

| Path | Why | |------|-----| | package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lock | Lock files are auto-generated — edits can corrupt dependency resolution | | Gemfile.lock, poetry.lock, Cargo.lock, go.sum, composer.lock | Same for non-JS ecosystems | | Dockerfile, docker-compose.yml | Infrastructure config — changes may affect production | | .github/workflows/, .circleci/ | CI/CD pipelines — unauthorized changes can trigger deploys | | .gitlab-ci.yml | GitLab CI config |

How it works

File tools (read, write, edit)

The extension checks the path parameter against the rules above. Read operations are more permissive (only .git/ is blocked).

Bash commands

The extension extracts path references from bash commands using regex and applies the same rules. Read-only commands (cat, grep, ls, find, head, tail, etc.) get the read-mode rules (more permissive).

Example: cat .git/config → blocked. cat node_modules/lodash/package.json → allowed. echo "test" > node_modules/foo.js → blocked.

Behavior

| Mode | Action | |------|--------| | Interactive | Shows dialog explaining which path is protected and why | | Non-interactive | Blocks with descriptive reason |

Status bar

Shows 🔒 path-guard in the footer when active.

Installation

Already active — lives in ~/.pi/agent/extensions/safety-path-protection/index.ts and auto-loads with every pi session.

Example

🔒 Protected file
  .github/workflows/deploy.yml

  CI/CD configuration — confirm before editing

  Allow?

  [Yes]  [No]