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

@rotastellar/cli

v0.1.0

Published

rotastellar — the developer CLI (bring-your-own-workload: login / build / push / run / results)

Readme

@rotastellar/cli

npm version node license install size

The developer CLI for RotaStellarbring your own workload: package your program, push it, run it on the orbital compute fleet, and fetch the results, all from your terminal.

A thin, self-contained wrapper over the authenticated RotaStellar control-plane API. No external dependencies; requires Node ≥ 18.

RotaStellar is in private beta. You'll need an account and an API key — request access at rotastellar.com.

Install

npm install -g @rotastellar/cli

This puts a rotastellar command on your PATH.

Quickstart

# 1. authenticate (stores creds in ~/.rotastellar/config.json)
rotastellar login --key <your-api-key>

# 2. push a workload and run it
rotastellar workload push ./my.wasm --name my-detector --kind eo.triage
rotastellar workload run pkg_xxxxxxxx@1

# …or push + run in one step
rotastellar workload run ./my.wasm --name my-detector

# 3. follow it and fetch results
rotastellar workload results <workload_id>
rotastellar workload results <workload_id> -o ./out      # download result artifacts

Commands

| Command | What it does | |---|---| | rotastellar login --key <api-key> [--url <base-url>] | Save credentials. | | rotastellar workload build <file.wasm> [--kind k] [--caps a,b] | Dry-run: show the content id + manifest locally; nothing is uploaded. | | rotastellar workload push <file.wasm> --name <n> [--kind k] [--caps a,b] | Content-address + register your program. | | rotastellar workload run <package_ref \| file.wasm> [--name n] [--objective o] | Submit a workload. A .wasm path is pushed first, then run. | | rotastellar workload results <workload_id> [-o ./out] | Status, outcome, and result artifacts; -o downloads them. | | rotastellar workload list | List your packages. | | rotastellar workload types | List the valid --kind values and their capabilities. |

Configuration

Credentials live in ~/.rotastellar/config.json (base_url, api_key). You can override per-invocation with environment variables:

| Variable | Overrides | |---|---| | ROTASTELLAR_URL | the control-plane base URL | | ROTASTELLAR_API_KEY | the API key |

Capabilities for a workload are resolved automatically per --kind; override them with --caps a,b.

How it works

The CLI never moves bytes through a browser. push content-addresses your program and uploads it directly to object storage via a short-lived presigned URL; run submits by package reference. The result artifacts are either custodied for you (content-addressed) or delivered to your own sink if you configured one.

Support

License

Apache-2.0.