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-gate

v0.1.2

Published

Trilho A: scaffolds the pi coding agent + quality gates + ao-compatible JSONL evidence into a project. npx pi-gate init.

Readme

ao-feedstock (pi-gate)

Trilho A: the usable-today path to "ask for a feature, get a reviewable PR".

It scaffolds three things into any project:

  1. the pi coding agent wiring (extensions that run your quality gates),
  2. your gate scripts (fast + full) and a CI hard backstop,
  3. an append-only evidence ledger (evidence/ledger.jsonl) whose vocabulary matches ao-by-codex — so the trust engine can ingest it later. Same family, separate repos, no fork. ao-feedstock is the raw material that feeds ao.

Quick start

# in the project you want the agent to work on:
npx pi-gate init
npm i -g @earendil-works/pi-coding-agent
pi
# then: "implement feature X"

What init writes

.pi/
  settings.json
  extensions/gates.ts     tool_result(write|edit) -> fast-gate ; agent_end -> full-gate
  extensions/secrets.ts   block secret-leaking bash ; redact secrets from output
  lib/evidence.ts         ao-shaped JSONL emitter (helper, not an extension)
  prompts/pr.md           PR prompt (commit convention + checklist)
gates/
  fast-gates.sh           typecheck + lint (runs only what exists)
  full-gate.sh            full suite
.github/workflows/ci.yml  the gate that actually blocks the PR
AGENTS.md                 rules for the agent (auto-fix ladder, no secrets, no auto-merge)
evidence/SCHEMA.md        the JSONL <-> ao EDN contract
package.json              + scripts gate:fast / gate:full (Node/hybrid projects)

Supported stacks

Auto-detected by the gate scripts — only tools that actually exist run:

| Stack | Detected by | fast-gate | full-gate | |--------|------------------|----------------------|--------------------------------------------------| | Node | package.json | tsc, lint script | tsc, lint, test, coverage | | Python | pyproject.toml | ruff | ruff, mypy, bandit*, pytest (+cov floor*) | | PHP | composer.json | pint | pint, phpstan, pest | | any | .git present | — | gitleaks* (secret scan) |

* = only when the tool is installed — gates never force a dependency. Coverage floor: install pytest-cov and it activates at GATE_COV_MIN (default 65). Python tools resolve from .venv/bin/ first, then PATH. Hybrid repos (e.g. Python backend + Node frontend manifest) run every matching stack. Pure Python projects don't get a package.json forced on them — the pi extension calls the gate scripts via bash directly.

CI adds the heavier security layer per the staged-gates principle (local fast, CI blocking, nightly heavy): gitleaks over full history, npm audit --audit-level=high (Node), bandit + pip-audit (Python).

The loop

pi "implement X"
  -> edits files       -> fast-gate per edit  (red -> steer "fix it")
  -> tries to finish   -> full-gate           (red -> steer "don't finish")
  -> /pr               -> opens PR ; CI is the hard backstop
  -> you review + merge

Status

v0, smoke-tested live against @earendil-works/pi-coding-agent v0.79.1 + DeepSeek.

Verified live:

  • Agent implements a feature end-to-end via pi -p.
  • fast-gate fires on each write/edit; full-gate fires at agent_end.
  • Evidence written to evidence/ledger.jsonl in ao vocabulary (see examples/ledger.example.jsonl), all events sharing one run/id.
  • Red path: a red suite at finish produces gate/decision permitida?:false and the steer message forces the agent to keep working until green (permitida?:true) — even in print mode.

Known limitation — secrets are a speed-bump, not a wall:

  • secrets.ts blocks naive secret-leaking bash (literal token / env var), but a determined agent can route around it (e.g. base64-encode the value).
  • tool_result redaction does not cover the agent's own assistant message, so a model that narrates a secret in its reply still leaks it.
  • Real secret control = don't expose secrets to the agent + CI secret scanning. The bundled ci.yml runs gitleaks as that hard gate (blocks the PR if a secret reaches the repo). Treat secrets.ts as the in-loop first line only.

The CLI and the evidence emitter are plain Node and run as-is.

Roadmap (not built yet)

  • pi-gate export --edn — convert ledger.jsonl to EDN for ao ingestion.
  • pi-gate doctor — check pi install + gate tooling.