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

oxiremote

v0.1.67

Published

Self-hosted remote-access agent — terminal, files, preview, remote desktop over a Cloudflare tunnel.

Downloads

784

Vulnerabilities

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

Links

Git

Maintainers

nhteranhtera

Keywords

remoteterminaltunnelself-hostedcloudflareddeveloper-tools

Readme

oxiremote (npm wrapper)

Thin wrapper around the OxiRemote Rust binary. Installing this package downloads the right prebuilt binary for your platform from the corresponding GitHub release and exposes it as oxiremote on your $PATH.

npm install -g oxiremote
oxiremote

The wrapper exists so users with npm in their muscle memory get the same one-command install as curl ... | sh. The wrapper version always tracks the upstream release version 1:1.

Environment variables

  • OXIREMOTE_BINARY_URL — override the base URL the postinstall fetches from (corp proxies, mirrors, air-gapped installs).
  • OXIREMOTE_GITHUB_REPO — override the source repo (default nhtera/oxiremote).
  • OXIREMOTE_VERSION — pin a specific binary version (otherwise tracks package.json).
  • OXIREMOTE_DISABLE_INSTALL=1 (alias OXIREMOTE_SKIP_INSTALL=1) — skip postinstall entirely.
  • OXIREMOTE_FORCE_DOWNLOAD=1 — re-download even if the version marker matches.
  • OXIREMOTE_OPTIONAL_INSTALL=1 — exit 0 on failure so a bad release doesn't break unrelated npm install runs.
  • OXIREMOTE_SKIP_GLIBC_CHECK=1 — bypass the Linux glibc compatibility check (only meaningful when you know what you're doing).

How it works

  1. npm install triggers scripts/install.js.
  2. The script detects process.platform/arch, picks the matching Rust target triple, and (unless bin/oxiremote.version already matches) downloads oxiremote-<version>-<target>.tar.gz (or .zip on Windows) plus oxiremote-<version>-sha256.txt from the GitHub release.
  3. SHA256 is verified, the archive is extracted into bin/, a Linux glibc compatibility check runs, and the executable bit is set. The version marker is written so re-installing the same version skips the network entirely.
  4. bin/oxiremote.js is a tiny shim that spawns the platform binary with inherited stdio.

A prepublishOnly lifecycle hook (scripts/verify-release-assets.js) HEAD-checks every release URL + verifies the SHA256 manifest names every asset before npm allows publish — so a tag without a matching release can never be published from a clean checkout.

The same checksum manifest is verified by oxiremote update, so the wrapper and the self-update path share one trust boundary.

License

MIT — see the upstream repository.