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

@sdkfixturelab260904/parcel-events-cli

v1.3.1

Published

Agent-first API CLI generated by the Doctorine SDK Foundry (sdkSha 79ada5ca4ce0).

Readme

parcel-events-cli

Command-line access to the API — JSON out, predictable errors, built for scripts and agents.

19 command(s). Identity: parcel-events-cli --provenance.

Quick start

npx --package @sdkfixturelab260904/parcel-events-cli parcel-events-cli --help
npm install -g @sdkfixturelab260904/parcel-events-cli
parcel-events-cli shipments list
parcel-events-cli find shipments

Development (from this package): npm run build && node dist/src/cli.js --help.

Usage

parcel-events-cli find <query>                      # search the catalog (JSONL)
parcel-events-cli resolve --operation-key "GET /…"  # bind the stable id
parcel-events-cli <group> <command> [flags]         # call the API
parcel-events-cli <group> <command> --schema        # JSON schema of the command input
parcel-events-cli <group> <command> --dry-run       # print the exact request; send nothing
parcel-events-cli <group> <command> --mock          # schema-shaped example; no network
parcel-events-cli --schema                          # index catalog (add --full for pagination objects)
parcel-events-cli --profile staging <group> <cmd>   # merge ~/.config/parcel-events-cli/config.toml
parcel-events-cli completion bash                   # shell completion (also: zsh | fish)

Base URL: --base-url → PARCEL_EVENTS_CLI_BASE_URL → the spec default.

Authentication

Credentials come from the environment — the CLI never prompts. Flag overrides env.

| Variable | Used for | | --- | --- | | PARCEL_EVENTS_API_KEY | API key (header Parcel-API-Key) | | PARCEL_EVENTS_BEARER_TOKEN | Bearer token |

parcel-events-cli auth status reports which variables are set (values are never printed). parcel-events-cli auth env prints the export template.

Runnable groups (first fully satisfied wins; smallest if several): api_key; bearer_token.

Webhooks

parcel-events-cli webhooks verify|listen|replay verifies inbound signatures. Secret: --secret or PARCEL_EVENTS_CLI_WEBHOOK_SECRET. Listen binds 127.0.0.1 and prints JSONL.

Output

  • Success → stdout as JSON (default), or --format jsonl|pretty|table|toon|yaml (--raw forces JSON)
  • Errors → one JSON line on stderr with a stable kind
  • Slice results → --transform <dot.path>

Command reference

See COMMANDS.md and SKILL.md. Specs over 20 MiB generate locally.

Exit codes

| Code | Meaning | | ---: | --- | | 0 | Success | | 1 | Findings (e.g. --fail-on-deprecated) | | 2 | Usage / bad flags | | 3 | Config | | 4 | Auth | | 5 | Forbidden | | 6 | Not found | | 7 | Conflict | | 8 | Rate limited | | 9 | Server | | 10 | Version skew | | 124 | Timeout | | 130 | Interrupted |