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

agentprint-cli

v0.1.1

Published

Find the keys and agent files AI coding agents leave behind, before they ship in your package. Runs the agentprint Python CLI through uvx or pipx.

Readme

uvx agentprint
npx agentprint-cli

Why

  • Agent files leak into packages. In April 2026 Lakera reported that of about 46,500 npm packages it scanned, 428 shipped .claude/settings.local.json, and 33 files in 30 packages held credentials.
  • We measured it too. Our pilot scan (5 November 2026, counts only) of the newest 1,976 npm packages and 1,997 PyPI releases found agent files in 2.1% of npm packages and 9.2% of PyPI releases. 1 npm and 6 PyPI packages shipped files that should never ship. No key-shaped strings turned up inside those agent files.
  • History files keep what you paste. Agents save prompts as plain text in your home folder. A June 2026 Hermes Agent advisory (CVE-2026-53870) covers such files being created readable by every user on the machine.

Quickstart

uvx agentprint scan      # sweep this machine and folder (keys masked)
uvx agentprint fix       # make the safe fixes; shows the plan and asks first
uvx agentprint install   # arm each agent it finds with the tripwire
uvx agentprint pack      # preflight: what your package would publish

On Windows, install adds the MCP server and the note but no agent hook yet (the hooks run through /bin/sh), so no agent hook blocks a publish or push there, and agentprint status says "MCP and note; no hook on Windows yet". agentprint protect (below) still checks pushes and npm publishes at git and npm themselves. scan, fix and pack work the same.

Get started has the details, including running from a clone of this repo.

For a team, a project config and baseline accept what you have already reviewed.

What it checks

| ID | What it finds | Severity | |---|---|---| | AP001 | An API key sits in an agent's history, transcript, paste cache, edit backups or chat database. | high | | AP002 | An API key sits in an agent settings or allowlist file, or inside an agent file in a package or push. | critical | | AP003 | An over-broad permission lets the agent run any command or skip every prompt, such as Bash(*) or bypassPermissions. | medium | | AP004 | An agent hook calls the network, with curl, wget, nc, a pipe into a shell, or a URL. | medium | | AP005 | An API key is written inline in an MCP server entry (env, headers, args, command or URL). | critical | | AP006 | An agent file, such as .claude/settings.local.json, would ship in your npm or PyPI package. | high, medium or low, by file | | AP007 | A personal agent file, such as CLAUDE.local.md, is in a git repo but not gitignored, or is already committed. | low | | AP008 | Agent history, settings or a key store can be read by other users on this machine (macOS, Linux and Windows). | medium; high for key stores | | AP009 | Source maps, original source or AI instruction files in your package hand an AI your code. | high to low by licence; no licence, UNLICENSED, SEE LICENSE IN, proprietary or only LicenseRef- choices count as closed; low for a private registry | | AP010 | A skill, rule, plugin or hook an agent loads has hidden characters, sends a credential out, pipes a download to a shell or hides a command. | high; critical for a credential sent out, medium for a piped download (low in install docs), low for a stray character or an unfinished read | | AP011 | An MCP server runs a package or image with no fixed version (npx, uvx, pipx run, docker run): each start gets whatever was published last. | medium |

Keys are found by pattern and are never used or sent anywhere: Anthropic, OpenAI, GitHub, AWS, Stripe, Slack and Google, then 27 newer rules (and Slack xapp- tokens): Google OAuth client secrets (GOCSPX-), publishing tokens (npm, PyPI, GitLab, Docker Hub), AI providers (Hugging Face, Groq, OpenRouter, xAI, Perplexity, Replicate), developer platforms (Supabase, Cloudflare, DigitalOcean, Linear, Notion, Shopify, Atlassian, Postman, SendGrid, Doppler, 1Password), and DeepSeek, Twilio, Discord and Telegram only next to the provider's name. A generic "secret-looking name = random-looking value" rule catches the rest. Format lengths for Docker Hub, Supabase secret keys and Google OAuth secrets are from third-party scanners, not the vendor's docs.

It also finds keys hidden from ordinary secret scanners: split across strings, behind invisible characters, continued across lines, inside YAML blocks or base64. The benchmark scores agentprint, gitleaks and trufflehog the same way on a labelled corpus, with its method and limits stated.

Inside your AI agent

  • A hook runs before the agent publishes a package or runs git push, and checks what would go out. It follows what the command runs, too: shell scripts, make and just recipes, npm version hooks. Not on Windows yet: there install adds only the MCP server and the note.
  • An MCP server gives the agent tools to check on its own.
  • If something would leak, the agent gets a brief: the fix steps, plus what to ask you (rotate a key).
  • It only ever blocks (BLOCK or CLEAR); your agent's own approval rules still apply.
  • Strict mode (agentprint install --strict) also blocks a publish or push agentprint can't check.
  • agentprint uninstall takes out exactly what install added.
  • agentprint protect adds a second check at git and npm themselves (a pre-push hook and prepublishOnly), so a push hidden from the agent hook is still caught. --undo takes it out.
  • Rather add it as a plugin? Claude Code, Codex, Copilot CLI, Gemini CLI, Cursor, Antigravity and Hermes each have one: see Plugins.

Details: Inside your agent.

More

Agents · Plugins · Use in CI · Privacy · Comparison · Census · How it works

Contributing · Security · License (MIT)

Built with Python 3.11+, uv, typer, rich, the MCP Python SDK, pytest and ruff; docs with Astro Starlight.