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

memman

v0.1.0

Published

Local web UI to visualize, edit, create and delete Claude Code memory files.

Readme

meman

A tiny local web UI to visualize, edit, create, and delete the memory files that Claude Code keeps under ~/.claude/projects/<project>/memory/.

Each memory is a markdown file (--- frontmatter + body). This tool renders them as structured cards grouped by type (feedback / project / reference / user), lets you edit the fields in place, and keeps the hand-curated MEMORY.md index in sync when you delete a memory.

Run

cd memory-manager
npm install
npm start
# → http://localhost:4785

The memory directory is auto-detected from your current working directory using Claude Code's project-slug scheme. Override it explicitly when needed:

node server.js --dir ~/.claude/projects/-home-me-myproject/memory
node server.js --dir <path> --port 5000
# env vars also work: MEMORY_DIR=... PORT=... npm start

If several project memory dirs exist and none matches the cwd, the tool prints the candidates and asks you to pass --dir.

Later: run on the fly

package.json declares a bin, so once published:

npx meman --dir <path>

What it does

  • Edit — change name / description / type / body per card. Hidden frontmatter (node_type, originSessionId) is preserved untouched, and flat vs. nested frontmatter files round-trip in their original format.
  • Create — "+ New memory" writes a properly-formatted file (nested format). Note: it does not auto-add a MEMORY.md index line — that index is curated by hand, so add the pointer yourself if you want the memory recalled.
  • Delete — moves the file to memory-manager/.trash/ (soft delete) and removes its reference from MEMORY.md: a bullet whose only link is that file is dropped; a bullet that bundles several links keeps the others.

Safety

  • All file access is confined to the resolved memory dir; filenames are validated (^[A-Za-z0-9_-]+\.md$) and path traversal is rejected.
  • Deletes are soft (recoverable from .trash/).
  • MEMORY.md is only ever touched on delete, never on edit/create.