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

@zanii/memory

v0.1.1

Published

Provable agent memory: a memory.write receipt that hash-chains what an agent remembered and when (salted content commitments, tamper-evident links) so an auditor can prove 'why did it decide that?'.

Readme

@zanii/memory

Provable agent memory. A memory.write receipt hash-chains what an agent remembered and when — so an auditor can answer "why did it decide that?" and prove the memory wasn't edited after the fact.

Each entry commits its content with a salt (the raw memory never leaves your system) and links to the previous entry's entry_hash — a tamper-evident chain. The entry_hash is an RFC 8785 canonical hash (@zanii/core), so a chain written in TypeScript verifies byte-identically in Python.

npm install @zanii/memory @zanii/core

Usage

import { appendMemory, verifyMemoryChain, verifyContent } from '@zanii/memory';

// write a chain — appendMemory auto-links prev + increments seq:
const a = appendMemory(null, { content: 'user asked for a refund', kind: 'observation', ts });
const b = appendMemory(a,    { content: 'policy allows refund within 30 days', kind: 'fact', ts });
const c = appendMemory(b,    { content: 'issued the refund', kind: 'decision', ts });

await agent.record(c.target, c.payload);   // keep c.salt to prove the content later

// audit: the chain is intact (nothing inserted, deleted, or edited):
verifyMemoryChain([a, b, c]).ok;           // true

// prove what a specific entry actually remembered:
verifyContent('issued the refund', c.salt, c.payload.content_commitment); // true

buildMemoryWrite(input) builds a single entry when you manage prev/seq yourself. verifyMemory(payload) checks one entry's entry_hash is self-consistent (catches an edited entry); verifyMemoryChain(entries) also checks the links and that seq increments.

Changelog

  • 0.1.0 — initial release: commitContent / verifyContent, buildMemoryWrite, appendMemory, verifyMemory, verifyMemoryChain.

License

Apache-2.0.