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

@swalvo/cli

v0.1.0

Published

Official CLI for the Swalvo hosted platform — manage projects, API keys, and rooms from the terminal; wire up a local app for RTC development.

Readme

@swalvo/cli

Swalvo from the terminal — manage projects, API keys, rooms and live streams, and wire up a local app for RTC development.

Part of Swalvo, open-source real-time communication infrastructure.

Install

npm install -g @swalvo/cli

Or run it without installing:

npx @swalvo/cli --help

Use

swalvo login                    # authenticate
swalvo whoami                   # who am I, against which deployment
swalvo projects create my-app   # create a project
swalvo keys create              # mint an API key for it
swalvo init                     # scaffold Swalvo into the app in this directory
swalvo dev                      # run against a local stack

Inspect a running deployment:

swalvo rooms list
swalvo connections list
swalvo rtc servers list         # the SFU fleet
swalvo diagnostics
swalvo errors list
swalvo logs
swalvo status

swalvo <command> --help documents each group. Also: chat, streams, sdk, config, version, logout.

Self-hosting

Point the CLI at your own deployment rather than the default:

swalvo config set apiUrl https://api.your-swalvo-deployment.example
swalvo config get apiUrl
swalvo config list

swalvo config stores local CLI preferences only — never secrets.

Headless use and configuration

| Variable | Purpose | | --- | --- | | SWALVO_TOKEN | Session token for CI and machines without a browser (beats stored credentials) | | SWALVO_API_URL | Overrides the configured API URL for one process | | SWALVO_DASHBOARD_URL | Dashboard origin used by swalvo login | | SWALVO_CONFIG_DIR | Where the CLI keeps its files (default ~/.swalvo) |

swalvo init links a directory to a project through a swalvo.json file (safe to commit).

Upgrading from the raven CLI

The CLI was renamed from raven to swalvo. The raven command still works for now and prints a deprecation notice; RAVEN_* environment variables are still read (with a one-time warning), an existing ~/.raven directory is read when ~/.swalvo has no file yet, and a directory's raven.json is used when it has no swalvo.json. Nothing is moved or deleted for you.

Documentation

License

MIT