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

@mutmutco/hub

v4.5.149

Published

Install and maintain the MMI CLI and every present host surface from one release-gated Hub command.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

jervaisejervaise

Keywords

Readme

@mutmutco/hub

mmi-hub is the public MMI maintenance command. It converges the current CLI and every host surface present on the machine through the release-gated Hub bill of materials, and owns the one hourly schedule that keeps them current.

Published from mutmutco/MMI-Hub.

Install

npm install -g @mutmutco/hub
mmi-hub install

install converges immediately, then enables hourly automatic updates by default.

Commands

mmi-hub status              what is installed, whether auto-update is on, anything to fix (default)
mmi-hub install             update everything now, then turn on hourly auto-update
mmi-hub update              update everything to the newest release now (--dry-run previews)
mmi-hub autoupdate on|off   turn hourly auto-update on or off; off keeps installed tools

Flags: --json (machine output), --dry-run, --verbose, --quiet, --no-color, --version, --help.

status and the no-argument command are read-only. They never install, heal, create state, change the schedule, or clean a repository.

Every screen is drawn by the shared installer face (@mutmutco/installer-face), so status, update and the rest use one layout and one set of words. Glyphs and colour appear only on an interactive terminal (NO_COLOR and --no-color respected); piped, the same screen prints as plain text:

mmi-hub - Mutatis Mutandis
Here's where things stand.
updater 3.1.1 - already current
cli 3.1.0 -> 3.1.1 - update available
auto-update on - hourly
mmi-hub has an update available.
Latest release: 3.1.1.
Next: mmi-hub update
  • update/install print one row per surface (plus the launcher row that keeps the one-line installer current), then a closing box with the verdict and one command.
  • autoupdate on|off prints one line: Auto-update is on. mmi-hub checks for updates every hour. or Auto-update is off. Installed tools were kept.
  • Refusals (unknown command, a failed step) go to stderr as Error: <sentence> with the command to run next.
  • --json keeps its machine shapes; --version piped prints the bare version.

State remains under ~/.mmi/updater (override with $MMI_UPDATER_HOME) so existing journals and the MMI Fleet Updater Windows task continue in place.

@mutmutco/[email protected] was the final historical compatibility release and remains installable for existing lockfiles. Its mmi-updater wrapper delegates to the exact-version @mutmutco/hub: old reconcile/run, install, uninstall, and verify/stamp calls map to mmi-hub update, install, autoupdate off, and status respectively. New installs and all releases after 3.137.0 use only @mutmutco/hub / mmi-hub.