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/monitor

v0.2.0

Published

Independent Zanii log monitor: continuously verify the transparency log is append-only (consistency proofs) and that anchored checkpoints hold. Makes 'trust no one' operational.

Downloads

202

Readme

@zanii/monitor

An independent watchdog for a Zanii transparency log. "Trust no one, including Zanii" is only a claim until someone continuously checks it — this is that someone. It verifies each Signed Tree Head's signature, proves the log is append-only (a consistency proof from the last size it saw — rewriting past history fails this), and confirms every anchored checkpoint is still an append-only prefix of the current tree. Any violation is surfaced loudly.

Run it as a library or the zanii-monitor CLI. Node 18+.

npm install @zanii/monitor

CLI

# watch continuously, persist state, POST alerts on violation
zanii-monitor --server https://ledger.zanii.agency --interval 60 \
  --state ./monitor.state --alert https://your-app/alert

# one-shot for CI/cron — exits 1 on any violation
zanii-monitor --server https://ledger.zanii.agency --once

Persisting --state across runs is what makes an offline rewrite impossible to hide: the next check proves the log is consistent with the size you last verified.

Library

import { checkOnce, monitor } from '@zanii/monitor';

const r = await checkOnce('https://ledger.zanii.agency', previousState);
if (!r.ok) console.error('VIOLATION:', r.violations);
// persist r.state and pass it back next time

await monitor('https://ledger.zanii.agency', {
  intervalMs: 60_000,
  onViolation: (r) => pageOncall(r.violations),
});

What it checks

| Check | Proves | |---|---| | STH signature | the tree head really came from the log operator | | Consistency (last size → now) | the log is append-only — no past entry was altered, removed, or reordered | | Anchor validity + extension | the current tree is an append-only extension of every on-chain checkpoint |

MonitorResult = { ok, size, root, checks[], violations[], state }. Persist state.

Changelog

  • 0.1.0 — initial release: checkOnce, monitor, and the zanii-monitor CLI.

License

Apache-2.0.