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

@prontohq/cli

v0.1.1

Published

Command-line interface for Pronto — B2B sales intelligence

Downloads

200

Readme

@prontohq/cli

pronto — command-line interface for Pronto, the B2B sales-intelligence platform. Search leads and accounts, enrich contacts in bulk from CSV, manage lists, and stream buying-intent signals to your webhook — all from your terminal or a shell script.

Install

# npm (no global install needed)
npx @prontohq/cli --help

# global install
npm install -g @prontohq/cli

# Homebrew
brew install prontohq/pronto/pronto

Authenticate

Get an API key at https://app.prontohq.com/settings/apis/keys, then:

pronto login pk_live_xxx
# or
export PRONTO_API_KEY=pk_live_xxx
pronto whoami

Credentials are stored at ~/.config/pronto/credentials.json with mode 0600. PRONTO_API_KEY always wins over the saved file; --api-key on any command wins over both.

Quick examples

# Preview an account search (sync, free)
pronto accounts search --preview --keyword '"sales agency"' --company-size 11-50

# Start an async lead search and poll until it finishes
JOB=$(pronto leads search --job-titles 'Head of Sales' --limit 50 --format json | jq -r .id)
pronto jobs status "$JOB" --watch

# Bulk-enrich contacts from CSV (async; prints enrichment_id)
pronto contacts enrich --batch leads.csv --enrichment email \
  --webhook-url https://my.app/webhooks/pronto

# Dry-run to see credit cost first
pronto contacts enrich --batch leads.csv --enrichment phone --dry-run

# Export a list to CSV
pronto lists export <list-id> -o list.csv

# Buying signals → webhook stream
pronto signals hiring --webhook-url https://my.app/hook \
  --selected-titles 'Account Executive' --published-date last_7_days

Output

--format json|csv|table — default is table on a TTY and json otherwise (so pipes work). -o file.csv writes to disk. Errors go to stderr; the exit code identifies the failure class:

| code | meaning | |---|---| | 0 | success | | 1 | Pronto API error | | 2 | invalid input | | 3 | authentication | | 4 | rate limit | | 5 | credits or plan limit |

Configuration

pronto config list
pronto config set base_url https://staging.prontohq.com/api/v2
pronto config set default_format json
pronto config get base_url

Config lives at the platform's standard XDG location (~/.config/pronto/config.json on Linux/macOS).

Development

npm install
npm run dev -- whoami           # run via tsx without building
npm test
npm run typecheck && npm run lint
npm run check:schemas           # diff against pronto-api-doc

To point at a sibling pronto-api-doc checkout other than the default:

PRONTO_API_DOC_PATH=/path/to/pronto-api-doc npm run check:schemas