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

@agenttrace/cli

v0.1.7

Published

AgentTrace — AI Agent observability. One command to monitor your agents locally.

Downloads

800

Readme

agenttrace

AI Agent observability. One command to monitor your agents locally.

Install

npm install -g agenttrace

Quick start

agenttrace onboard                    # First-time setup + configure provider keys
agenttrace start                      # Start server, proxy, and dashboard

Commands

| Command | Description | |---------|-------------| | agenttrace onboard | First-time setup — generate token and configure provider API keys | | agenttrace start | Start the server, proxy, and dashboard | | agenttrace status | Show current configuration | | agenttrace reset-token | Generate a new auth token | | agenttrace providers list | List configured providers | | agenttrace providers set <name> <key> | Set/update a provider API key | | agenttrace providers remove <name> | Remove a provider |

Options (for start)

| Flag | Default | Description | |------|---------|-------------| | --port | 8080 | API server / dashboard port | | --proxy-port | 4000 | LLM proxy port | | --retention-days | 30 | Data retention period in days | | --no-open | — | Don't auto-open the browser |

Provider API key management

The proxy can manage provider API keys so your app doesn't need to know them. Configure keys during onboard or with the providers subcommand:

agenttrace providers set openai sk-proj-...
agenttrace providers set anthropic sk-ant-...
agenttrace providers list

When a request goes through the proxy, the correct auth header is injected automatically:

  • OpenAI / Mistral / Cohere / DeepSeek / Moonshot / Zhipu / MiniMax / Baichuan / Yi → Authorization: Bearer <key>
  • Anthropic → x-api-key: <key>
  • Google → x-goog-api-key: <key>

If the client already provides its own auth header, the proxy does not override it.

Security

Provider API keys are stored securely:

  • macOS: System Keychain (OS-managed encryption, per-app access control)
  • Linux desktop: libsecret / GNOME Keyring (OS-managed encryption, D-Bus session scoped)
  • SSH / headless: AES-256-GCM encrypted file (application-managed, machine-derived key)

Keys are never stored as plaintext in config files. At runtime, keys are decrypted once at startup and held in memory only.

Rate limiting

You can set per-provider rate limits during onboard, or edit ~/.agenttrace/config.json directly:

{
  "token": "...",
  "providers": {
    "openai": {
      "rateLimit": { "maxRequests": 100, "windowSeconds": 60 }
    }
  }
}

When the limit is exceeded, the proxy returns 429 with a Retry-After header.

License

Apache-2.0 — see LICENSE.

Part of the AgentTrace monorepo.