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

forge-memory

v0.2.71

Published

Guided Forge installer and local runtime manager for the Forge UI, OpenClaw, Hermes, Codex, and iOS pairing.

Vulnerabilities

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

Links

Git

Maintainers

albertbuchardalbertbuchard

Keywords

Readme

forge-memory

Single-command Forge install:

npx forge-memory

This is the preferred setup path for Forge. The command launches a guided CLI that installs the local Forge UI/runtime first, then discovers OpenClaw, Hermes, and Codex and offers to configure the detected adapters against the same Forge data folder.

Development install from a Forge checkout:

npx forge-memory --dev

The Forge UI/runtime is always installed. The adapter checkbox list only contains host integrations, with detected adapters selected by default and missing adapters shown as disabled rows. You can skip adapter setup during install and return later with configure.

Useful commands:

npx forge-memory configure
npx forge-memory status
npx forge-memory doctor
npx forge-memory ui
npx forge-memory restart
npx forge-memory stop
npx forge-memory export
npx forge-memory uninstall
npx forge-memory pair-ios

pair-ios prefers the Iroh QR. Forge starts a Rust Iroh host, prints a QR payload with the desktop node id, pairing token, optional relay hint, and ALPN forge-companion/1, and the iPhone app connects through its native Rust bridge. Use --manual-http only when you intentionally want a LAN, Tailscale, or direct HTTP/TCP route.

The base install stays one command on purpose. The detailed companion transport reference lives in the Forge repo at docs/companion-iroh.md and in the published docs at https://albertbuchard.github.io/forge/companion-transport.html.

configure reruns the full guided flow using the current config as defaults. export writes a portable backup of the real Forge data folder. uninstall removes the Forge Memory runtime manager and cache while keeping the data folder by default; pass --remove-data only when you intentionally want the data deleted too.

Typical first run:

  1. Run npx forge-memory.
  2. Keep or change the real Forge data folder.
  3. Select OpenClaw, Hermes, and Codex adapters with Space.
  4. Pair the iOS companion when prompted, or skip and run npx forge-memory pair-ios later.

Manual OpenClaw, Hermes, and Codex commands still exist in the Forge repository for advanced recovery, source-linking, and adapter debugging. The normal user path should start here.