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

@cc-mem/core

v0.2.2

Published

Shared memory for coding agents, kept in Claude Code's auto memory: directory resolution, index loading and careful writes

Readme

@cc-mem/core

The core of cc-mem: one memory for all your coding agents, kept in the auto memory Claude Code already writes. The agent plugins build on it:

| Agent | Package | |---|---| | pi | @cc-mem/pi | | OpenCode | @cc-mem/opencode | | DeepSeek Harness | @cc-mem/dsh |

Install one of those to use cc-mem in an agent. This package is for scripts and for writing a plugin for another agent.

Command line

Print a project's memory index the way an agent sees it, for scripts or hooks:

npx @cc-mem/core index --project <dir>

Library

  • resolveLocation(env, project) resolves the memory directory as Claude Code does: the canonical git root, so worktrees share one memory; autoMemoryDirectory from user, local and managed settings; CLAUDE_CONFIG_DIR; the long-path hash. It also reports whether auto memory is turned off.
  • memoryText(env, project, { writable }) builds what the plugins put in the prompt: where the notes are, how to treat them, and MEMORY.md within Claude Code's limits of 200 lines and 25,000 characters.
  • writeMemory, editMemory and deleteMemory back the memory_write, memory_edit and memory_delete tools.
    • They check Claude Code's frontmatter format.
    • They never overwrite a file on create.
    • They delete one named memory file at a time, never MEMORY.md.
    • They record which agent wrote or changed a file.
  • listDescription, writeDescription, editDescription, deleteDescription and fileNameDescription are the tool descriptions, shared so the tools read the same in every agent.

Use systemEnv() for the environment of the current process.

License

MIT. Not affiliated with or endorsed by Anthropic. "Claude" and "Claude Code" are trademarks of Anthropic.