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

@hivemagnus/magnus

v2.3.7

Published

Install, upgrade and roll back a Magnus server and console with one command: `npx @hivemagnus/magnus init`, then `magnus upgrade`. Pins exact, tested component versions, backs up PostgreSQL before every migration and reverts automatically when the new ver

Readme

@hivemagnus/magnus

Install, upgrade and roll back a Magnus server and console with one command.

npx @hivemagnus/magnus init       # create and start a project in ~/.magnus
magnus upgrade                    # newest release of the current major, with backup and auto-revert
magnus rollback                   # back to the previous version
magnus status                     # versions, health, history, available updates

Each release of this package pins exact, tested versions of @hivemagnus/magnus-server, @hivemagnus/magnus-ui and @hivemagnus/magnus-contracts, together with the matching agent version. The pins and release notes ship as magnusRelease in package.json.

magnus init

init creates a managed project: the configuration, the installed versions and the units that run them.

~/.magnus/
  magnus-project.json            project state and history
  package.json, package-lock.json  exact pins of the serving release
  config/magnus-server.env       generated secrets (0600)
  config/magnus-ui.env
  config/tls/                    self-signed certificate (unless --tls-cert/--tls-key)
  data/                          server data (MAGNUS_HOME: audit logs, rotation state)
  versions/1.1.0/                one npm install per release
  current -> versions/1.1.0      what the services run
  backups/                       pre-migration database dumps
  units/                         the generated systemd units
  deps.compose.yml               PostgreSQL and Redis, when no --database-url/--redis-url is given

| Option | Meaning | |---|---| | --system --service-user NAME | System units in /opt/magnus (run as root) instead of user units | | --database-url URL --redis-url URL | Use your own PostgreSQL and Redis instead of the bundled compose file | | --version X.Y.Z | Install a specific release | | --public-host NAME | Host name for URLs and the certificate | | --admin-user, --admin-password | Console login (the password is generated and printed once by default) | | --no-ui, --no-start, --no-auto-migrate | Server only; configure without starting; keep MAGNUS_AUTO_MIGRATE=false | | --supervisor none | Write everything, but start the processes yourself |

User services start at boot only with lingering enabled (loginctl enable-linger $USER).

magnus upgrade

magnus upgrade --dry-run     # releases, notes, new settings and migrations, without changing anything
magnus upgrade [--to X.Y.Z] [--yes] [--generate-secrets] [--allow-major] [--source DIR]

An upgrade:

  1. Checks the registry and the Node.js the services run (--node PATH switches it).
  2. Refuses a downgrade or a major-version change (unless --allow-major).
  3. Checks for new required settings, free disk space and the systemd session bus.
  4. Installs the release into versions/<X>.
  5. Runs the new version's configuration check and a start-up test, before the database is touched.
  6. Dumps PostgreSQL and migrates.
  7. Switches ./current, restarts and waits for the new version to serve.
  8. If the new version is unhealthy, switches back and prints the database restore command.

Slow or one-way migrations need --yes. An upgrade that is interrupted is recorded in magnus-project.json; finish it with magnus upgrade --resume or go back with magnus rollback.

magnus rollback [--restore-db] [--force]   # back to the previous version
magnus restore <dump>                      # stop, restore into a clean schema, start again

magnus-server upgrade hands the same command to the project it was installed into.

magnus adopt

Turns an existing npm install into a managed project without touching what runs:

npx @hivemagnus/magnus adopt --server-env-file /etc/magnus/server.env --ui-env-file /etc/magnus/ui.env

See UPGRADING.md for every upgrade path, agent upgrades and the switches that turn automation off.

Requires Node.js ^24.22.1 or ^26.13.0, npm, systemd (or --supervisor none), and openssl for the self-signed certificate.

License

Apache-2.0