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

@isaacthoman/pulpo

v0.91.0

Published

Operator-first command-line client for Pulpo

Readme

Pulpo CLI

Operator-first command-line client for a Pulpo instance.

npm install --global @isaacthoman/pulpo
pulpo context add production --url https://pulpo.example.com
pulpo auth login --email [email protected]
pulpo auth 2fa status
pulpo auth 2fa setup
pulpo auth 2fa confirm
pulpo settings export --output pulpo-settings.json
pulpo icon upload ./acme.svg --name Acme --mode monochrome
pulpo model test acme-model "Reply with a short greeting" --no-agent --preset reasoning=off

Use pulpo help or pulpo <command> --help for the complete command reference.

Model create and update files may configure chat preset and choice icons with any canonical Lucide name. Discover available names with pulpo model icons, or filter them locally with a query such as pulpo model icons camera. Invalid names are rejected before the model request is sent. Add --json for stable { "name": "..." } rows in scripts.

Test a newly configured model with pulpo model test <model-id> [prompt...]. The command requires exactly one of --agent or --no-agent, plus one explicit --preset <preset-id>=<choice-id> for every preset exposed by the model. It does not silently apply preset defaults. For example:

pulpo model test acme-model "Investigate the failing build" \
  --agent \
  --preset reasoning=high \
  --preset web-search=enabled

git diff | pulpo model test acme-model \
  --no-agent \
  --preset reasoning=off \
  --preset web-search=disabled

Model tests stream assistant text to stdout and use temporary chats by default. Pass --keep to retain the test in normal chat history, --no-stream to wait for the completed text, --json for one final result, or --jsonl for the replayable response event stream. Model testing requires a user session created by pulpo auth login; management tokens cannot access user chat endpoints.

The major command groups are context, auth, token, instance, settings, provider, lab, icon, model, user, usage, audit, workspace, banner, job, export, and backup. There is intentionally no restore command.

Human-readable tables are the default. --json reserves stdout for stable JSON; errors remain on stderr, and noninteractive destructive commands require --yes. Add --verbose to print method, path, status, and timing diagnostics without printing authorization headers or request bodies.

Configuration precedence is command-line options, then PULPO_CONTEXT / PULPO_URL / PULPO_TOKEN, then the current stored context. Context metadata lives in the platform config directory. Session tokens use Keychain on macOS or Secret Service on Linux when available, with a mode-0600 file and warning as the fallback. Passwords are read from a hidden prompt, stdin, or PULPO_PASSWORD; no secret-bearing password/token option is accepted. Authenticator and recovery codes use the hidden prompt or PULPO_2FA_CODE. Enrollment secrets and recovery codes are printed only when created; store them securely before continuing.

Settings exports use apiVersion: pulpo.dev/management/v1 and carry an opaque revision. settings diff exits with status 2 when changes exist. A stale settings apply fails rather than overwriting a newer change. Use a marker such as { "fromEnv": "KAGI_API_KEY" } for a secret replacement or { "clear": true } to remove it.

Management token scopes are account:read, account:write, instance:read, instance:write, catalog:read, catalog:write, users:read, users:write, usage:read, audit:read, operations:read, and operations:write. Administrator scopes continue to require the token owner's current administrator role. Tokens are shown only once when created and only work below /api/management/v1.

Deleting a model permanently reassigns its historical chats and usage to the hidden unknown model placeholder while retaining recorded token and cost totals. Active or queued model work must finish before deletion can proceed.