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

@spences10/pi-nopeek

v0.0.16

Published

Secret-reducing workflow reminder for credential-dependent Pi commands

Readme

@spences10/pi-nopeek

built with Vite+ tested with Vitest npm version license

my-pi package preview

Reduce accidental secret disclosure during credential-dependent commands. pi-nopeek reminds agents to use the nopeek CLI instead of reading or pasting .env, cloud-token, and database credential values into model-visible input.

Installation

pi install npm:@spences10/pi-nopeek

Local development from this monorepo:

pnpm --filter @spences10/pi-nopeek run build
pi install ./packages/pi-nopeek
# or for one run only
pi -e ./packages/pi-nopeek

What it does

The extension injects a system reminder telling the model to use pnpx nopeek ... or npx nopeek ... when it needs credentials from:

  • .env
  • .env.*
  • .tfvars
  • .tfvars.json
  • cloud CLI profiles or service credentials

It adds no slash commands and no custom tools.

Model reminder

The injected reminder tells the model to:

  • lead with pnpx nopeek run ... -- <command> in Pi, where each tool call starts an ephemeral shell
  • select only the keys required by the child command
  • use nopeek load only when the harness confirms persistent env-file injection, or when source/evaluation and execution occur in the same trusted shell
  • use pnpx nopeek list and pnpx nopeek status to inspect key names without values
  • use pnpx nopeek audit to scan for exposed secrets and gitignore coverage
  • avoid printing, echoing, catting, grepping, tracing, or pasting secret values into model-visible output

Example one-shot workflow:

pnpx nopeek run .env --only DATABASE_URL -- \
  sh -c 'psql "$DATABASE_URL" -c "select 1"'

run gives selected values only to its child process. That child can still disclose values through stdout, stderr, shell tracing, env, or printenv. A source_file produced by load does not carry into an unrelated Pi tool call.

pi-redact is a separate, best-effort last-mile safety net. It cannot guarantee arbitrary child output is safe. Review nopeek's threat model and non-goals before choosing a workflow.

Use npx instead of pnpx outside pnpm-oriented environments.

Using from a custom harness

import nopeek from '@spences10/pi-nopeek';

// pass `nopeek` as an ExtensionFactory to your Pi runtime

my-pi imports this package directly and enables it as the built-in nopeek reminder.

Development

Package scripts build transitive workspace dependencies first, then run local tools through Vite+ with vp exec.

pnpm --filter @spences10/pi-nopeek run check
pnpm --filter @spences10/pi-nopeek run test
pnpm --filter @spences10/pi-nopeek run build

License

MIT