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

@robbeverhelst/do

v1.105.0

Published

do — the agent-drivable CLI over the public /api/v1 surface

Readme

@robbeverhelst/do

do — an agent-drivable command-line client over the do public API (/api/v1). A thin HTTP client: per-tenant API-key auth, the same validation and RLS wall as the web app, no direct database access.

Published to npm as @robbeverhelst/do (the @do scope is taken); the installed command is do. The workspace package is named @do/cli internally.

bunx @robbeverhelst/do help
bunx @robbeverhelst/do today

Scope (v1)

The daily loop, all over /api/v1 with an API key — no destructive verbs:

  • capture "<text> #tag ! ~area" — quick-add a task to the inbox (! stars it)
  • today — actionable tasks (overdue / scheduled / due / in-progress)
  • task done <id> — complete (idempotent)
  • task snooze <id> [--days N | --until <date>] — reschedule
  • habit log <id> [--value N] [--at <iso>] — record a check-in
  • <entity> list / <entity> get <id> — read tasks, habits, occurrences, shopping-lists, inventory-items, recipes, meal-plans, notes, contacts, webhooks
  • login, config, whoami, help, version

Auth & config

Resolution order: --api-key/--url flags → DO_API_KEY/DO_API_URL env → ~/.config/do/config.json (written by do login / do config set).

Output

--json everywhere, and automatic JSON when stdout is piped (non-TTY). Failures print { "error": { code, message } } and exit non-zero (see do help --json).

Develop

bun run --filter '@do/cli' dev -- today   # run from source
bun run --filter '@do/cli' test           # bun:test suite
bun run --filter '@do/cli' compile        # standalone ./do binary

The full agent skill lives at docs/agents/do-cli.md; the authoritative surface is always do help --json.