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

openmhp-node

v0.9.1

Published

Turn a lab bench computer into an OpenMHP node: serve its instruments in the background, discoverable and safely operable by any AI agent. A thin, single-purpose companion to openmhp-cli.

Readme

openmhp-node

Turn a lab bench computer into an OpenMHP node: it keeps serving whatever instruments are wired into it — in the background, across reboots — so any AI agent elsewhere in the lab can find them and operate them safely.

Run this on the computer actually connected to the instrument (its USB port, its vendor software, its own network link). It's the companion to openmhp-cli, which you run instead on the computer where an agent lives — a scientist's laptop, say. This machine doesn't need an agent on it at all.

npx openmhp-node setup

It asks two questions — which folder holds your instruments' device packages, and which port to start counting from — installs a small background service, and starts it. From then on this computer answers automatically.

If there's nothing in that folder yet, point an agent at this machine and say "onboard my <instrument>" first; it writes the package for you. Then run setup again.

npx openmhp-node status   # is it installed, is it running
npx openmhp-node stop     # remove the service

Requires Node 18+ and Python 3.10+. Everything lives in ~/.openmhp. The background service uses systemd on Linux, a LaunchAgent on macOS, and your Startup folder on Windows (so on Windows it starts once you log in, not before).