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-provider-allowlist

v0.2.1

Published

Restrict pi coding agent to a single allowlist or blocklist of model providers. Single mode + 3-page wizard via /providers-allowlist.

Readme

pi-provider-allowlist

Restrict pi to a single allowlist or blocklist of model providers. Providers outside the policy are hidden from /model and --list-models — regardless of which API keys are set in your environment. Tool API keys (search, MCP, misc scripts) are never touched.

Install

pi install npm:pi-provider-allowlist

Uninstall: pi remove npm:pi-provider-allowlist. Trial without install: pi -e npm:pi-provider-allowlist.

Configure

Interactive (recommended): run /providers-allowlist in pi.

3-page wizard: 1/3 Mode (allowlist = only keep selected, blocklist = only hide selected) → 2/3 Members (Space toggle, a select all, Tab/←→ switch pages) → 3/3 Submit (preview visible/hidden, confirm). Empty selection = keep default (all visible, no file created).

Manual: create ~/.pi/agent/provider-allowlist.json:

{ "mode": "allowlist", "providers": ["anthropic", "newai"] }

or

{ "mode": "blocklist", "providers": ["openai"] }

Restart pi or run /reload to apply. New pi providers that appear later are filtered automatically on next session.

Fail-open by default: if the config file is missing or broken, no provider is filtered and a warning is printed. This prevents a broken config from locking you out of pi.

Verify

pi --list-models | awk '{print $1}' | sort -u   # only visible providers

In an interactive session, /providers-allowlist show prints current config.

How it works

At pi's provider registry level, not env vars:

  1. At startup enumerates known providers from ~/.pi/agent/models-store.json + models.json, and overrides hidden providers with empty model list (pi.registerProvider(name, { models: [] })).
  2. On session_start re-scans via ctx.modelRegistry.getAvailable() and re-applies (also after /reload).
  3. First startup with no config pops the 3-page wizard (TUI only, Esc to cancel).
  4. Env vars (EXA_API_KEY, BRAVE_API_KEY, etc.) are never modified.

Limitations

  • --list-models without a session relies on models-store.json cache; on fresh installs filtering may be incomplete until the store exists.
  • Hiding uses pi.registerProvider() override (verified but not documented as "hide"); re-applied each startup.
  • pi.unregisterProvider() only affects dynamically-registered providers; restoring built-in providers requires /reload (noted in UI).

Development

mise run check   # tsc + tests + npm pack dry-run
├── src/
│   ├── index.ts     # Extension entry (pi.extensions)
│   ├── filter-ui.js # 3-page wizard (pi-tui custom)
│   ├── core.js      # Pure logic (zero deps, unit-tested)
│   └── core.d.ts
└── test/            # node --test

MIT licensed.