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

@codingcoffee/pi-privacy-filter

v0.1.0

Published

pi extension that redacts PII/secrets before sending to the LLM and restores them in responses

Readme

pi-privacy-filter

A pi extension that runs every prompt through a local privacy classifier (openai/privacy-filter via @huggingface/transformers) before it is sent to the LLM, and transparently restores the original values in the LLM's response.

user input ──► [redact] ──► LLM
                  │
                  └── placeholder→original mapping (in memory)

LLM response ──► [unredact via mapping] ──► you see the real values

Example:

  • you type: My AWS account number is 22922829292
  • LLM sees: My AWS account number is [ACCOUNT_NUMBER_1]
  • you see: ... My AWS account number is 22922829292 ... (assistant's reply, restored)

The mapping lives in memory for the session only — nothing is written to disk by this extension. Your original message is still stored in the session file (since that's where pi keeps it); only the bytes leaving for the model are redacted.

How it works

  • Hooks the context event to mutate the deep-cloned messages pi is about to send to the model. User messages and tool results have their text run through the classifier; matched spans are replaced with stable placeholders like [ACCOUNT_NUMBER_1].
  • Hooks the message_end event to swap any placeholders back to their original values in the assistant's finalized message before pi displays / persists it.
  • Identical values reuse the same placeholder for the whole session.

Install

cd pi-privacy-filter
npm install   # or: bun install

Then wire it into pi using any one of:

Quick test

pi -e ./index.ts

Project-local

mkdir -p .pi/extensions
ln -s "$PWD" .pi/extensions/pi-privacy-filter

Global

mkdir -p ~/.pi/agent/extensions
ln -s "$PWD" ~/.pi/agent/extensions/pi-privacy-filter

Or via pi settings (~/.pi/settings.json)

{
  "extensions": ["/absolute/path/to/pi-privacy-filter"]
}

Commands

  • /privacy-mapping — dump the current placeholder→value mapping (handy for debugging).

Files

  • index.ts — the extension
  • sample.ts — original standalone POC (bun run sample.ts)