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

ranla-cli

v0.19.1

Published

Ranla CLI — drive Ranla from your terminal or coding agent: browser sign-in, Ranla's commands, approvals, and the email API

Readme

ranla-cli

Drive Ranla from your terminal or coding agent (Claude Code, Codex, Cursor…): sign in through the browser, run Ranla's commands, handle approvals, and send email with the Ranla API.

npx -y ranla-cli@latest login        # prints a link: approve it in the browser
npx -y ranla-cli@latest whoami
npx -y ranla-cli@latest run help     # Ranla's commands: campaign, segment, page, …

No API key to copy: login prints a link and a code, you approve it in the browser for the workspace you pick, and the CLI saves its own key in ~/.config/ranla/config.json. In a coding agent the command exits with the link; after you approve, run login again to finish.

Ranla's commands

ranla run help                     # every noun and its verbs
ranla run help campaign            # a noun's verbs with every field
ranla run campaign list
ranla run <noun> <verb> --input '{"field":"value"}'   # or --file input.json, or --input - (stdin)

Anything that sends, publishes or spends waits for approval instead of running:

ranla approvals list
ranla approvals approve <id>
ranla approvals reject <id>

Choose what Ranla thinks with: Included, or your own OpenRouter, Anthropic, OpenAI or Google key. The key is read from standard input (or a variable you name), never from the command line, and is tested with one tiny call before it is saved:

ranla brain                                   # what she thinks with; saved keys show their last 4 characters
pbpaste | ranla brain key openai              # or: ranla brain key openai --key-env OPENAI_API_KEY
ranla run brain use --input '{"choice":"included"}'

Output is JSON when piped and text at a terminal (--json forces JSON). Errors go to stderr; exit 1 means the request failed, 2 means the command line was wrong.

Workspaces

Each sign-in is one workspace. ranla login --workspace "<name>" adds another, ranla workspaces list shows them, ranla workspaces use "<name>" picks one, and --workspace "<name>" on any command uses it once. With several and none picked, commands ask instead of guessing.

Email API

ranla emails send --from [email protected] --to [email protected] --subject "Hi" --text "Hello"
ranla domains list

After login these use the saved key. RANLA_API_KEY (or SUPERSENDTX_API_KEY) overrides it, for CI and servers. Defaults to https://api.ranla.ai; RANLA_API_URL or --base-url points elsewhere. ranla logout revokes the CLI's key and removes it.

When a newer version is on npm, the CLI prints one line to stderr (never stdout) saying so. It checks at most once a day. Turn it off with RANLA_CLI_NO_UPDATE_CHECK=1 or NO_UPDATE_NOTIFIER=1; it is always off when CI is set.

Guide: https://docs.ranla.ai/guides/agent-cli

License

MIT