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

@x12i/doctor-x

v1.0.41

Published

Doctor-X — metadata-driven diagnostic and remediation CLI

Readme

Doctor-X CLI

Doctor-X is a CLI-powered playbook runner for machine, network, and service diagnostics/remediation.

Two commands

| Where | Command | What it does | |-------|---------|--------------| | Any station (usually your console) | doctor-x play -s <playbook> | Start the playbook. Queues remote work when needed. | | Target machine | doctor-x work | Do the queued work. No flags needed. |

Example:

# Console — start once
doctor-x play -s wg-ingress

# Gateway server — just work
cd ~/x-doctor-shared-space
doctor-x work

Install

npm install -g @x12i/doctor-x@latest
doctor-x --version

Shared folder

No prior init required — use the all-in-one doctor-x-space playbooks:

# File server (once)
doctor-x play -s doctor-x-space-host

# Every other station (once)
doctor-x play -s doctor-x-space
# or: doctor-x play -s doctor-x-space-client

These create or connect to the canonical share name doctor-x-space, then initialize Doctor-X on that station automatically.

Manual init still works:

doctor-x init --shared-space "<path-to-shared-folder>"

--host is optional. On a handoff target you can also cd into the shared folder and run doctor-x work without init.

Playbook aliases

  • wg-ingresswg-public-endpoint-ingress-regression
  • doctor-x-space / doctor-x-space-client → platform client playbook (mount/map + init)
  • doctor-x-space-host → platform host playbook (create share + init)
  • smb-mount / smb-persistent-mountsmb-share-persistent-mount (Linux persistent SMB mount)

Check situation on any station

doctor-x status

Shows shared folder, all known stations, pending jobs, handoffs, and latest run results.

Check everything this station knows

doctor-x check

Runs all applicable checks: CLI install, shared folder read/write, station identity, fleet/job state, and scenario-specific probes (WireGuard on Linux gateway, SMB mount, etc.).

doctor-x check              # on Linux gateway — includes root-required probes
doctor-x check --group wireguard # only WireGuard readiness
doctor-x check --json

Resume after a failure

doctor-x resume

On the console (x2) this re-runs the last failed playbook. On the gateway (x9) it runs doctor-x work. On Linux the CLI auto-elevates with sudo (preserving your PATH for nvm/fnm) when root is required — just run doctor-x resume.

doctor-x resume --dry-run   # show plan only
doctor-x resume --json
doctor-x status --host gateway-server
doctor-x status --json

SSH option

To run a remote target from the console without handoff:

doctor-x context set-host gateway-server --ssh-host 192.168.10.31 --ssh-user root --default
doctor-x play -s wg-ingress