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

rigscope

v0.2.6

Published

Your machines, in view. A self-hosted Linux system and process monitor.

Readme

Rigscope

Your machines, in view. A self-hosted Linux system and process monitor.

View CPU, memory, GPU, disk and network readings, browse History, inspect running processes and set alerts. Run a hub for the dashboard and a collector on each machine you want to monitor. The default installation runs both on this computer.

Install

Requires Linux, Node.js 26+ with npm, and systemd for background services.

npx --yes rigscope@latest install --boot

Save the generated owner password and open the printed dashboard URL (normally http://127.0.0.1:8081). The services keep running after you close the terminal. --boot starts them at boot; omit it to start at login instead.

Add ~/.local/bin to PATH to use rigscope. You can also run ~/.local/bin/rigscope directly. No global npm install or source checkout is needed.

To try Rigscope in the terminal before installing services:

npx --yes rigscope@latest try

The trial uses separate data and stops with Ctrl+C.

Use it

| Task | Command or guide | | --- | --- | | Check services and the dashboard URL | rigscope status | | Follow hub logs | rigscope logs hub --follow | | Upgrade from npm | rigscope upgrade | | Delete installation and all saved data | rigscope uninstall | | Remove installation, preserve saved data | rigscope uninstall --keep-data | | Stop or start the installation | rigscope stop / rigscope start | | Open the dashboard through Tailscale HTTPS | Set up remote access | | Monitor another machine | Add a collector | | Enable junction/VRAM GPU temperatures | rigscope gpu-temps enable | | Enable CPU package power (RAPL) | rigscope cpu-power enable | | Install a downloaded package | Install from an archive |

Each collector connects outbound to up to eight hubs. Each hub has its own users, permissions, history and alerts. Collectors need no incoming ports.

What to expect

Rigscope is read-only: it does not kill processes, change priorities or control services on monitored machines. Missing sensor readings stay unavailable. NVIDIA and available AMD GPU counters are supported; Intel GPU readings are partial. On NVIDIA GDDR6/6X/7 cards Rigscope can additionally report junction and VRAM temperatures from GPU registers once the collector is granted BAR0 read access (GPU monitoring). See the hardware notes.

History is RAM-only by default: recent charts are bounded in memory and telemetry history disappears when the hub restarts. Users, credentials, enrollment, settings and alert state remain persistent. Opt into compact SQLite summaries with HUB_TELEMETRY_MODE=persistent, or start an explicit recording when you need a saved incident snapshot. Process details are fetched while you view them and are never saved to History. See Monitoring and alerts and telemetry storage for retention, sharing, freshness and notification behavior.

Documentation

| Guide | Covers | | --- | --- | | Installation | npm, HTTPS, collectors, upgrades and hardware | | Operations | Diagnostics, backups, recovery and archive deployment | | System installation | Dedicated service accounts and system units | | Configuration reference | Environment variables and source enrollment | | Monitoring and alerts | Data limits, sharing, users and webhooks | | Telemetry storage | RAM vs persistent history, recording and benchmark | | Sensor readings / Exports | Reading meanings and downloads | | Development / Architecture / Design | Source setup and implementation references | | Releasing / Release notes | Publishing checks and version changes | | Scale validation | Synthetic measurements on one host; no capacity guarantee |

Published on npm. Maintained by Triet (@Triet1402). Licensed under MIT; see dependency notices. Report vulnerabilities privately using SECURITY.md.