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

@chitmark/cli

v0.6.5

Published

CLI for Chitmark by Open Agent Ledger: trust decisions on agent-mediated actions (verify, feedback, challenge) from the terminal

Readme

@chitmark/cli

Terminal interface for Chitmark: trust decisions on agent-mediated actions (verify / feedback / challenge). Wraps @chitmark/sdk.

Score a signup from the command line, walk an interactive TUI, or script all three verbs in CI. Verdicts render as JSON with decision-coded exit codes.

npm version

Requires Node >= 24.

Install

npm install -g @chitmark/cli

Auth

export CHITMARK_API_KEY=ck_live_...
# optional
export CHITMARK_BASE_URL=https://api.chitmark.com

Or pass --api-key / --base-url per command.

Commands

Interactive mode (default)

On a terminal, chitmark verify with no flags opens an Ink TUI: pick an action with the arrow keys, walk through subject fields (email / IP are hashed client-side), review, and run. The verdict renders as a colored panel: green ALLOW, yellow CHALLENGE, red DENY, with confidence bar, reasons, principal, and a [v] toggle to inspect verdictToken claims.

chitmark verify        # interactive
chitmark feedback      # interactive: eventId, outcome, value (unit asked only with a value)
chitmark challenge     # interactive: eventId, method, session

In the verdict panel: enter/q done, r re-run, c copy eventId, v claims.

Flag mode (scripting / CI)

Passing the required flags skips the TUI and prints JSON. Same on non-TTY (piped input) or with --json.

# Verify an action
chitmark verify \
  --action signup \
  --email [email protected] \
  --ip 203.0.113.7 \
  --session sess_9f3a \
  --surface app.acme.com/signup

# Report credit burn (store eventId from verify on the account)
chitmark feedback --event-id evt_2f9c --outcome credit_burn --value 87.4

# Issue a challenge
chitmark challenge --event-id evt_2f9c --session sess_9f3a \
  --prefer payment_preauth,proof_of_work

# Force JSON on a terminal
chitmark verify --action signup --json

Timeouts and transport errors return a degraded challenge verdict (exit 2) and never an allow.

Exit codes

| Code | Meaning | | :--- | :------------------------------------------------------------- | | 0 | Explicit non-degraded allow only | | 2 | challenge, degraded, or any non-allow decision (fail closed) | | 3 | deny | | 1 | error (bad flags, auth, network) |

Script on the exit code, parse the JSON for the details. Unknown decisions never exit 0.

Global options

| Flag | Default | Purpose | | :------------------- | :----------------- | :----------------------------------------- | | -k, --api-key | CHITMARK_API_KEY | API key | | -u, --base-url | production API | API base URL override | | -e, --env | production | production / staging / development | | -t, --timeout <ms> | 800 | Client timeout; validated positive integer | | --pii-mode <mode> | hashed | hashed / raw / none | | -j, --json | off | JSON output, skips the TUI |

Operator notes

  • --session is a binding id you supply: prefer a high-entropy, server-generated value (UUID v4 / CSPRNG). It binds challenge and verdictToken; reuse it across verify → challenge → re-verify for that attempt only. Client-generated or guessable values weaken binding.
  • The default --user-agent is chitmark-cli, and a non-browser UA scores like automation: expect challenge on signup-shaped verifies unless you pass a real browser UA with --user-agent.
  • --value must be a finite number; --unit is usd | credits | count (default usd) and ships only alongside a value, matching the SDKs. Optional --source is label provenance (billing | usage_metering | trust_queue | manual_review | customer_system | automated_detector).
  • Invalid --timeout or --value fail fast with a local error: no API call is made.
  • Verdict tokens: every signed JWT requires kid. Respect JWKS Cache-Control / ETag (and Last-Modified when present) via conditional requests; refresh on unknown kid (see Verdict tokens). Empty JWKS means verification is impossible: fail closed (local unsigned.<eventId> is not a trust path).

Agent integration

Using Cursor, Claude Code, Codex, or another coding agent? Point it at chitmark.com/SKILL.md, or paste this into your prompt: Integrate Chitmark into my app following https://chitmark.com/SKILL.md.

Resources

License

Proprietary: see LICENSE.