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

meetsoma

v0.2.0

Published

Soma — the AI coding agent with self-growing memory

Readme

σ Soma

Memory isn't retrieval. Memory is change.

npm install -g meetsoma
soma

Docs · Blog · Hub · Source


An AI coding agent that grows with you. Identity, protocols, and muscle memory — all evolving through use, not configuration.

Most agents forget everything between sessions. Soma doesn't.

Install

npm install -g meetsoma

This installs the Soma CLI — a thin bootstrap layer. On first run, it downloads the full agent runtime (~50MB) from GitHub.

What Happens

npm install -g meetsoma     ← installs CLI only (~50KB)
soma                        ← first run: downloads agent runtime
soma                        ← every run after: starts a session

Requirements: Node.js ≥ 20.6, git, an API key (Anthropic, Google, or OpenAI).

First Run

cd your-project
soma

Soma detects your project (language, framework, package manager, monorepo signals), creates .soma/, and writes its own identity. By session two, it remembers.

Commands

CLI (from your shell)

soma                         # fresh session
soma inhale                  # resume from last session's preload
soma -c                      # continue last session (full history)
soma -r                      # pick a session to resume
soma focus <keyword>         # prime for a topic
soma map <name>              # boot with a workflow MAP

soma doctor                  # project health + migration check
soma status                  # infrastructure health check
soma --version               # show agent + CLI versions
soma --help                  # full command reference
soma --help scripts          # list installed scripts
soma --help commands         # all CLI + TUI commands

Session (inside the TUI)

/exhale          save state + write preload for next session
/breathe         save + rotate into fresh session
/inhale          check preload status
/rest            disable keepalive + exhale
/pin <name>      keep a muscle/protocol hot
/kill <name>     drop to cold
/hub install     install from the community hub
/soma doctor     run migration analysis

Two Versions

Soma has two independently-versioned layers:

σ  Soma v0.7.1       ← agent version (the runtime — features, protocols, templates)
   CLI v0.2.0        ← CLI version (this npm package — install flow, delegation)

The agent version is what matters for features. The CLI version is the bootstrap.

Updating

soma init                    # update the agent runtime
npm install -g meetsoma      # update the CLI (rare)
soma doctor                  # check if project .soma/ needs migration

The Five Ideas

Identity — a self-written file. It knows your project, your patterns, your stack.

Protocols — behavioral rules. "Read before write." Hot ones load. Cold ones fade.

Muscles — learned patterns. Correct it twice → permanent learning.

Breath — inhale, work, exhale. No compaction. Full context every session.

Heat — attention management. Used things stay. Unused things cool.

How It Works

~/.soma/agent/              ← global runtime (git clone, updated via soma init)
your-project/.soma/         ← per-project memory (identity, protocols, sessions)

The CLI delegates to the runtime. The runtime loads your project's .soma/, resolves the identity chain (project → parent → global), and boots the agent with your accumulated context.

On boot, Soma silently adds any missing settings or protocols from newer versions (Tier 1 auto-fix). Bigger migrations are handled by /soma doctor inside the TUI.


BSL 1.1 © Curtis Mercier — open source 2027