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

@slayzone/computer

v0.42.0

Published

SlayZone computer — remote execution node (pty, git, fs, processes)

Readme

@slayzone/computer (SlayZone computer)

A SlayZone execution node. Dials OUT to a hub using a join token (mint one on the hub; wss:// for any hub that is not on this machine), then runs terminals/agents/git on this machine.

SLAYZONE_HUB_JOIN_TOKEN=<token from the hub> slayzone-computer

The join token embeds the hub URL, so nothing else is required.

Standalone computers automatically follow each connected hub's exact npm release, even when a protocol mismatch prevents the normal connection. Downloads and native runtime checks run in a private staging directory. A replaceable connector attaches to the persistent session host, preserving running terminals/jobs, enrollment, allowed roots, output buffers, and session hook/CLI addresses. Different hubs may run different releases when their local host contracts are compatible.

Candidates complete a 60-second connection probation before becoming current. Failures roll back, retry with exponential backoff and jitter, and quarantine repeatedly failing releases for 15 minutes. Supervisor updates preserve the host; host updates wait until all work finishes. Incompatible host contracts report maintenance required and wait for the same safe maintenance window. Node and npm must be available, and the computer ROOT must be writable.

To disable automatic release changes, set "autoUpgrade": false in <ROOT>/computer.config.json, or SLAYZONE_COMPUTER_AUTO_UPGRADE=0, then restart. Desktop-managed computers use the app updater. Hub computer details show progress, errors and next retry; local status lives under <ROOT>/computer-runtime/hubs/<hub-host>/upgrade-status.json.

Existing monolithic releases need one planned migration restart after active work finishes. Later connector/supervisor upgrades need no VM access. The hub must advertise its published release on /health. Explicit service stop/restart still ends running work. Production migration and cloud validation are separate rollout steps.

This runs the launcher in the FOREGROUND. It recovers child crashes, but does not start again after logout or reboot. To install it as a supervised service instead, use the CLI:

npm install -g @slayzone/cli
slay computer create <name> --token <token from the hub>

GPL-3.0-only. Source: https://github.com/debuglebowski/slayzone