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

@userelay/cli

v0.2.0

Published

Relay from your terminal — start migrations, watch them, answer them, see what they cost.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

eshwarankrishnan1eshwarankrishnan1

Keywords

Readme

@userelay/cli

Relay from your terminal.

npm install -g @userelay/cli

export RELAY_BASE_URL=https://relaymesh.io   # your deployment
pbpaste | relay login                        # paste a key from Settings

Or pass it per command: relay --url https://relaymesh.io runs list.

CI should set RELAY_API_KEY instead of logging in — the environment always wins over the stored config, so a machine behaves the same as the command you tested by hand.

There is no default host. The CLI attaches a live API key to every request, and a fallback domain we do not own would receive it on the first misconfiguration. It refuses to run instead — which also means moving the service later is one environment variable, not a republish.

relay runs start --source salesforce --dest attio --live --watch
relay runs list
relay runs show run-2026...
relay runs reply run-2026... "skip Deal_Registration__c"
relay credits
relay usage run-2026...

relay runs approve needs a key minted with the runs:approve scope. Ordinary keys can start migrations and read the plan, but not sign off on writing to a customer's live system — that's the point.

Everything here goes over HTTP through @userelay/sdk. There is no database client in this package, deliberately: one implementation per verb, and the one we use daily is the one customers use.

License

Apache-2.0. See LICENSE and NOTICE.