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

@arcolab/arcops

v0.5.0

Published

Agent-first ops cockpit CLI for the Arcops backend (Stripe revenue, traffic, GSC, UTM/funnels, customers, postmaster inbox).

Readme

arcops

arcops - agent-first ops cockpit CLI for the Arcops backend (Stripe revenue, traffic, GSC, UTM/funnels, customers, postmaster inbox) across all your sites.

Single binary, ~115 KB, one runtime dep (picocolors). Built for both humans (TTY) and AI agents (pipe): stdout is always machine-consumable data, stderr carries all progress/diagnostics, and every failure exits non-zero with a structured error envelope.

Install

npm install -g @arcolab/arcops
arcops auth login --token <api-key>

Requires Node 20+. The default API is https://arcops.cc (override with --api or ARCOPS_API).

New here? (invite -> first data)

Onboarding is invite-gated and self-service. With a valid invite code you provision your own org and mint your own key over public routes — no admin hand-off. Full walkthrough (with the exact request shapes) is the Cold start section of SKILL.md; the short version:

  1. Get an invite code — an admin runs arcops invite create --org-name "<Your Org>" (the --org-name code provisions a new org on redeem).
  2. Sign up with the code: POST https://arcops.cc/api/auth/sign-up/email with {email, password, name, inviteCode} (or the browser page https://arcops.cc/login?invite=<code>) — creates your account + org and returns a session.
  3. Mint an org-scoped API key with that session: POST https://arcops.cc/api/auth/api-keys — copy the plaintext key once.
  4. arcops auth login --token <api-key> — then arcops site ls, revenue, traffic, verbs.

API keys are org-scoped Better Auth keys minted at one of three scopes — read, write, send — and are never created by the CLI (legacy ts_… tokens are still accepted via dual-read but no longer issued).

Agent reference

The full agent-facing reference lives in SKILL.md - install, the three scope tiers, cold-start walkthrough, the agent-first contract, output/error semantics, idempotency for the send verbs, common-task recipes, and the generated verb reference. It is the single source of truth; this README does not duplicate it.

The verb catalog is generated from src/verbs/registry.ts (the same source arcops verbs --json serializes) via bun run gen:skill; a drift test fails CI if SKILL.md and the registry diverge.

Development

bun install
bun run dev          # bun --watch run src/main.ts -- (pass CLI args after --)
bun run build        # bundles to dist/arcops.mjs with shebang + version inject
bun test             # bun test
bun run typecheck    # tsc --noEmit (must pass before commit)
bun run gen:skill    # regenerate SKILL.md verb reference from the registry

Project notes (architecture, two-repo workflow, gotchas) are in AGENTS.md (repo-only; not shipped in the npm package).