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

@memora-hq/memora-verifier

v0.1.0

Published

Offline verification of Memora local evidence: .memora bundles and on-disk session stores. No network calls, no native/OS-specific dependencies.

Readme

@memora-hq/memora-verifier

Offline verification for Memora local evidence — .memora bundles and on-disk local session stores. No network calls, no hosted service, no native or OS-specific dependencies.

This package answers: given evidence produced on a machine (a bundle someone exported, or a session recorded on disk), is it internally consistent? Signature recovery, event-chain lineage, payload hashes, and manifest continuity all get checked here, entirely offline.

npm install @memora-hq/memora-verifier

What's in here

| Module | Purpose | |---|---| | bundle.ts | Read, export, and verify .memora evidence bundles (verifyBundle, readLocalBundle, exportLocalBundle) | | verify.ts | Verify an on-disk local session store end-to-end (verifySession) | | store.ts | LocalEvidenceStore — the on-disk layout a session is read from | | session.ts | LocalSession and encryption-key derivation for a session | | manifest.ts | Sign and verify a session's execution manifest | | identity.ts | Local signing identity (an Ethereum-style keypair) and its on-disk key file |

Who uses this

  • memora-sdk — the CLI's offline .memora bundle verifier (tier 1 of the two-tier verification story: offline first, API-backed second).
  • memora-local — the desktop app's capture engine, for reading back and verifying what it just recorded. Capturing itself (spawning a PTY, watching the filesystem) is not in this package — see "What's deliberately not here" below.

What's deliberately not here

This package verifies evidence; it does not produce it. Nothing here spawns a process, opens a pseudo-terminal, or touches Electron. If you're looking for live session capture (runLocalCommand and friends), that lives in memora-local, which depends on this package — never the other way around.

Naming note

verifyBundle/verifySession are the current names. verifyLocalBundle/verifyLocalSession are kept as deprecated aliases of the same functions for existing callers; new code should use the short names.

License

Apache-2.0