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

remxo

v0.1.1

Published

Remote execution for humans and agents

Readme

remxo

Remote execution for humans and agents.

This package is a thin native launcher. It contains no Rust code and no prebuilt binary of its own: it resolves the exact-version platform package for your process.platform and process.arch, validates it, and hands your argv to the native remxo executable.

Install

npm install -g remxo

Requires Node.js 18 or newer.

Release candidates are published to the rc dist-tag instead: npm install -g remxo@rc.

Supported platforms

| Platform | Package | | --- | --- | | Windows x64 | @remxo/core-win32-x64 | | Linux x64 (glibc) | @remxo/core-linux-x64 |

Both platform packages are installed automatically as optional dependencies. A missing or version-mismatched platform package fails with an explicit error instead of falling back to some other remxo found on PATH.

Alpine/musl and other unlisted platforms need a separate native build and verification; the glibc package is not guaranteed to run there. macOS support is paused until a real Apple device is available for verification, so the current optional packages intentionally cover only Windows and Linux.

First run

The launcher does not print a banner and runs no install script. The native CLI guides you from your first command:

remxo init --lang zh-CN   # or: remxo init --lang en
remxo unlock              # master password, entered hidden with * feedback
remxo status
remxo hosts

remxo prod-01 df -hT
remxo --json prod-01 ls -la

On a fresh install remxo status reports an empty inventory and appends a Next: line naming the single command to run — remxo init, remxo unlock, or remxo host add <alias>, depending on how far setup has progressed. Once the Vault is unlocked and at least one host is registered, that line disappears so an established installation stays quiet. --json output is never extended with it.

Master and backup passwords must be at least 12 bytes and are only accepted at hidden interactive-terminal prompts.

What the launcher does not do

  • It never invokes a local sh -c or any other shell to start the core.
  • It has no postinstall step: nothing is downloaded, compiled, or updated at install or run time.
  • It never searches PATH for a remxo binary. REMXO_CORE_PATH exists only for development and isolated test fakes, and an empty or invalid value fails closed rather than silently falling back.
  • On Unix it uses execve with argv0 preserved; on Windows it spawns a direct child with inherited stdio and forwards exit codes and signals.

Security posture

Remxo is a development build without an independent security audit. Its security level is L1, not L2 same-user isolation. It does not claim absolute production safety and does not replace the authorization boundary of the remote account. It reuses the system OpenSSH client and does not disable host-key verification.

Credentials live in an encrypted Vault protected by a master password you enter yourself. Remxo never asks you to hand a password, private key, or passphrase to an AI agent or to another process.

Documentation

License

MIT