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

@getjuratify/verify

v0.1.1

Published

Offline verifier for Juratify evidence bundles

Readme

@getjuratify/verify

Offline verifier for Juratify evidence bundles. Runs entirely on your machine and requires no trust in Juratify servers: it recomputes hash chains, checks receipt and checkpoint signatures, rebuilds Merkle roots, and, given the workspace data key, decrypts every payload and checks it against its recorded hash.

The format it verifies is frozen in docs/evidence-format.md at the repository root.

CLI

npx @getjuratify/verify bundle.json
npx @getjuratify/verify bundle.json --data-key-file key.txt

Options:

  • --data-key <base64> workspace data key, enables payload decryption
  • --data-key-file <path> file containing the base64 data key
  • --json print the report as JSON
  • --quiet no output, exit code only

Exit codes: 0 all checks passed, 1 verification failed, 2 operational error (bad arguments, unreadable file, malformed input).

Chain, receipt, checkpoint, and key checks need no secrets. The data key additionally proves that each sealed payload decrypts and matches the hash the chain commits to.

Library

import { verifyBundle, parseDataKey, formatReport } from "@getjuratify/verify";

const report = verifyBundle(bundle, { dataKey: parseDataKey(keyBase64) });
if (!report.ok) {
  console.error(formatReport(report));
}

verifyBundle is pure and synchronous; it does no I/O.

License

Apache-2.0