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

@arial-ai/cli

v0.0.10

Published

Agent-first command-line interface for Arial — the agentic product analytics tool.

Readme

@arial-ai/cli

Command-line interface for Arial — the agentic product analytics tool.

Designed agent-first: every command emits structured output with explicit next-step instructions, making it usable by coding agents (Claude Code, Cursor, etc.) and by humans alike.

Install

npm install -g @arial-ai/cli
# or
npx @arial-ai/cli --help

Requires Node.js 20 or newer.

Quick start

# 1. Create a fresh workspace and receive an agent key
arial signup --name "My Project"

# 2. The agent key is saved to ~/.config/arial/config.json by default.
#    Verify it works:
arial whoami

# 3. Share the claim URL printed by `signup` with the human owner,
#    or have them run:
arial workspace claim <passphrase>

Commands

arial signup [--name <name>] [--no-save]   Create a workspace + agent key (unauthenticated)
arial login  [--key <key>] [--api-url <url>]  Save an API key for future commands
arial logout [--purge]                      Remove the stored API key
arial whoami                                Print the authenticated user

arial workspace list                        List workspaces visible to the current key
arial workspace show <slug>                 Show one workspace
arial workspace signup [--name ...]         Alias of `arial signup`
arial workspace claim <passphrase>          Claim a workspace as the current user

arial taxonomy list                         List canonical events shipped with Arial
arial taxonomy show <event>                 Show schema + properties + example
arial taxonomy context                      Show the universal context fields

Agent-friendly output

All commands accept --json for a stable envelope:

{
  "status": "ok" | "error",
  "command": "workspace.signup",
  "summary": "...",
  "data": { ... },
  "next_steps": [{ "action": "...", "command": "...", "reason": "...", "priority": "primary" }],
  "errors": [{ "code": "...", "message": "...", "hint": "..." }],
  "warnings": ["..."],
  "resources": [{ "label": "Docs", "url": "https://arial.sh/docs" }]
}

Exit codes:

| Code | Meaning | | ---- | ----------------- | | 0 | Success | | 1 | Unknown error | | 2 | Unauthorized | | 3 | Not found | | 4 | Validation error | | 5 | Network error |

Configuration

Settings are resolved in this order (later overrides earlier):

  1. ~/.config/arial/config.json (or $XDG_CONFIG_HOME/arial/config.json)
  2. Env vars: ARIAL_AGENT_KEY, ARIAL_API_URL
  3. Command-line flags (--key, --api-url)

Set ARIAL_CONFIG_DIR to override the config location entirely.

License

MIT