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

@nodatachat/protect

v3.1.0

Published

NoData's verification layer: the formats, specs, test vectors and verifiers that let anyone check NoData's claims without trusting NoData.

Readme

@nodatachat/protect: NoData's verification layer

This package lets you check NoData's claims without trusting NoData. It does not run NoData, has no CLI for the product and makes no network calls. It holds the formats, their specs, test vectors, and the code that checks them. The code is shipped readable (not minified) because it is meant to be read.

Looking for the old protect CLI (init, encrypt, run)? It moved to @nodatachat/nodata: npm i -g @nodatachat/nodata.

What you can check today

"NoData holds only half a key" (split-key format v1)

An API key or a secret is split on your computer into two 1024-byte halves. NoData stores one; your computer keeps the other and joins them in memory.

  • SPLIT-KEY-FORMAT.md: the whole format, what it proves and what it does not.

  • dist/split-key.js: the implementation (about 70 lines). NoData's software runs this same module.

  • Check that the code matches the published format:

    npx @nodatachat/protect@3 check-vectors

    It recomputes the vectors from the spec and prints PASS or FAIL. It needs nothing but Node.

What this proves: NoData's half is random bytes drawn apart from the value, so on its own it says nothing about the value, not even its length. What it does not prove on its own: that the software on your computer never also sends your half. You can watch that in the traffic: the only split material that leaves is the 1024-byte server half.

"Every decision leaves a proof you can check" (evidence pack format v1)

Every release, open, revoke or policy decision writes a signed receipt into a chain. An evidence pack is a JSON export of those receipts with their signatures and public keys.

  • EVIDENCE-PACK-FORMAT.md: the format, the exact bytes each signature covers (Ed25519, and ML-DSA-65 for the quantum-resistant half), the seven checks, and what a pack does not prove.

  • EVIDENCE-PACK-EXAMPLE.json: a complete pack signed with public test keys, so you can see every check pass and then break it.

  • Verify a pack you were given, or the example:

    npx @nodatachat/protect@3 verify-pack pack.json

    It prints PASS or FAIL for each check and exits 0 only if all of them hold.

Coming next

Each release adds only what is needed to verify a claim NoData makes: the file-seal format next.

Requires Node 20.19 or later. The one dependency is @noble/post-quantum, for ML-DSA-65, which Node does not provide.

License

FSL-1.1-ALv2. See LICENSE.md. You may read, run and verify freely.