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

sovereign-compute

v0.4.2

Published

Connect your CPU/GPU machine to the Sovereign optimization website. All solving runs locally on your computer.

Readme

sovereign-compute

Connect your CPU/GPU computer to the Sovereign optimization website.

The hosted backend is only a mediator: it receives jobs from the website, forwards them to your machine, stores the result, and returns it to the browser. All solving happens locally on your computer.

Install

npm install -g sovereign-compute

This installs:

  • the sovereign terminal command
  • the Sovereign solver binary for Windows x64 (bundled automatically)
  • on Windows x64, HiGHS 1.15.1 (highs-reference.exe, MIT) for the website's benchmark comparisons; Sovereign never calls it to solve your jobs
  • on Linux/macOS, a download is attempted during install when a release asset exists

No git clone or C++ build is required on Windows.

Connect your machine

sovereign connect --duration 8

Or with an explicit coordinator URL:

sovereign connect --server https://sovereign-we6b.onrender.com --duration 8

The terminal prints a pairing code. Enter it on the website under Machines → Connect with code, choose how long the machine stays connected, and leave the terminal running.

Configuration is saved to:

  • ~/.sovereign/config.json
  • ~/.sovereign/env

Commands

| Command | Purpose | |---|---| | sovereign | Pair and start the local worker | | sovereign start | Resume using saved config | | sovereign status | Show saved server/engine/expiry |

Optional flags

| Flag | Purpose | |---|---| | --server <url> | Coordinator URL (default: production Render backend) | | --engine <path> | Override the bundled solver binary | | --duration <hours> | Requested connection duration | | --name <label> | Machine name on the website |

Requirements

  • Node.js 18+
  • Outbound HTTPS access to the coordinator URL
  • For GPU jobs: an NVIDIA GPU and driver. The bundled Windows solver (1.2.0) loads the driver at run time, so no CUDA toolkit is needed; sovereign connect prints why CUDA is unavailable when it cannot be used
  • For HiGHS reference jobs: nothing extra on Windows x64. HiGHS runs single-threaded with the job's time limit and reports only its own solve time. Rebuild it with scripts/build-highs-reference.ps1

Architecture

Website -> Backend mediator -> Your PC worker -> Backend -> Website

No inbound firewall port is required on your computer.