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

egregore-init

v0.10.19

Published

Experimental Egregore installer — tests PATH-binary launcher and assistant selection. Not for production use.

Readme

egregore-init (experimental)

Alpha installer for Egregore. Not for production use. This is the current installer surface while the alpha flow is being hardened.

What's different in this alpha

  1. egregore is a real PATH binary, not a shell alias. Works immediately in the current shell and from any future shell. Multi-instance aware.
  2. Guided setup actually opens. The installer can launch the selected assistant at the end — no "open a new terminal" step.
  3. Alpha telemetry tag. Registrations and telemetry carry flow_variant: "alpha" so activation rates can be compared against the legacy flow.

Install

npx -y egregore-init@latest

Advanced flags:

  • --open — local founder mode (creates a new Egregore on GitHub)
  • --codex — prefer Codex for this local install
  • --claude — prefer Claude Code for this local install
  • --runtime <claude-code|codex> — explicit assistant selection
  • --no-autolaunch — don't launch the selected assistant at the end; useful for CI
  • --force — skip the in-repo detection check
  • --api <url> — override API URL

After install, the command stays the same:

egregore

Pick the Egregore instance, then pick the assistant for that launch. Scripted flows can still pass --runtime codex <slug> or --runtime claude-code <slug>.

Rollback

npm deprecate egregore-init --message "superseded"

Existing installs keep working — their local egregore binary and registry entries are self-contained.