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

autark-cli

v0.1.5

Published

CLI for autark — hypothesis-driven product runbooks. Track products, hypotheses, runs, and actions from the terminal.

Downloads

546

Readme

autark-cli

CLI for autark — hypothesis-driven product runbooks.

A product has hypotheses. Each hypothesis has runs. Each run logs actions (emails sent, posts made, replies received). The dashboard shows it all.

Install

npm i -g autark-cli

Login

autark login send [email protected]
# check inbox
autark login verify [email protected] --code 123456

Runbook use

Autark is ID-first. Use product list / context to discover IDs, then pass IDs for writes. slug/H01 remains a convenience alias.

autark product upsert --slug chrome-relay --name "Chrome Relay" --tagline "..."
autark product list   # prints slug, visibility, id, name
autark context chrome-relay

autark hypothesis create --product-id <product_id> --md @./H01.md --code H01 --title "..."
autark run start --hypothesis-id <hypothesis_id>
autark log action --run-id <run_id> --channel github --title "..." --url https://github.com/...
autark run finish --run-id <run_id> --narrative @./narrative.md

Mail use

autark mail covers the AgentMail surface Autark needs. It does not require a separate AgentMail CLI login.

autark mail setup --prefix laksh

autark mail send --run-id <run_id> \
  --to [email protected] \
  --subject "Subject" \
  --text @./body.txt

autark mail reply --run-id <run_id> --message-id <message_id> --text @./reply.txt

autark mail threads --limit 20
autark mail thread <thread_id>
autark mail messages --limit 20
autark mail message <message_id>
autark mail raw <message_id>
autark mail attachment --message-id <message_id> --attachment-id <attachment_id> --out file.bin

Mail sends/replies call AgentMail directly with the user's inbox-scoped key from ~/.autark/credentials.json, then log an Autark email action containing agentmail_thread_id and agentmail_inbox_id.

ENV

  • AUTARK_API_URL — override the default Worker URL (https://autark-api.kushalsokke.workers.dev)
  • AGENTMAIL_API_URL — override AgentMail API base
  • AGENTMAIL_API_KEY, AGENTMAIL_EMAIL, AGENTMAIL_INBOX_ID — override local mail credentials for debugging

Architecture

The CLI is a thin HTTP client over a Cloudflare Worker that holds the InstantDB admin token. Magic-link auth via InstantDB. Token saved to ~/.autark/credentials.json after login.

The Worker uses the AgentMail org key only for provisioning and dashboard thread reads. Local mail send/reply uses the user's inbox-scoped key.