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

@onemem/cli

v0.6.3

Published

OneMem CLI — verify, inspect, and provision verifiable agent memory + traces from the terminal

Downloads

509

Readme

@onemem/cli

The onemem command-line tool — verify, inspect, and provision verifiable agent memory + traces from your terminal.

npm install -g @onemem/cli
# dashboard launcher support:
npm install -g @onemem/dashboard
# or
npx @onemem/cli verify <session-id>

Publication note, 2026-06-19: @onemem/[email protected] is current on npm and the public install path is proven: npm exec --yes --package @onemem/[email protected] -- onemem --version prints 0.6.2. pnpm registry:status --strict and pnpm release:preflight --strict --timeout 30 both pass. @onemem/dashboard is current on npm at 0.1.4.

Commands

| Command | What it does | Needs | |---|---|---| | onemem verify <session-id> | Independently re-verify a TraceSession's Merkle chain from chain data alone | nothing (read-only) | | onemem trace list | List recent sessions | nothing | | onemem trace get <session-id> | Session metadata (agent, status, call count) | nothing | | onemem trace events <session-id> | The decoded ActionCall chain (tool, link, content hash, Walrus blob) | nothing | | onemem health | Check RPC + package reachability | nothing | | onemem dashboard | Launch the local dashboard on localhost:4040 or --port <port> | @onemem/dashboard installed | | onemem login | Pair this terminal with a hosted dashboard callback and save ~/.onemem/credentials.json | hosted dashboard implementing the callback contract | | onemem init | Provision (or reuse) a namespace + ReadWrite cap — zero config | a Sui signer | | onemem namespace share <namespace-id> <recipient> | Mint + transfer a ReadOnly or ReadWrite namespace capability | signer + Admin cap | | onemem namespace revoke <cap-id> | Self-revoke a capability you hold | signer that owns the cap | | onemem namespace admin-revoke <namespace-id> <cap-id> | Admin-revoke a capability by ID; object remains but OneMem gates reject it | signer + Admin cap | | onemem namespace capabilities <namespace-id> | List active capabilities from namespace events | nothing (read-only) | | onemem add <text> | Store a memory + emit a verifiable ActionCall | signer + MemWal config | | onemem search <query> | Vector-recall memories | signer + MemWal config |

Global flags: --json (machine output), --network <testnet\|mainnet\|devnet\|local>.

The read-only commands (verify, trace *, health) need no signer, no Walrus, no Seal — anyone can independently verify a session. init resolves a signer the same way the SDK runtime does (env key → Sui keystore → a generated+persisted wallet). add/search need the signer plus MemWal env (onemem add prints exactly which vars are missing).

Not in v0.1 (deferred)

  • Runtime installers (onemem install --runtime …) — each runtime already has its own one-line install; a unified installer is post-hackathon.

Full command spec: docs/05-our-architecture/05-cli/command-surface.md.