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

@manya-hael/ledger

v1.0.0

Published

Federated audit ledger: every event that crosses the bus gets tamper-evidently chained — composed from stamp and unify.

Readme

@manya/ledger

A federated, tamper-evident audit trail. unify's event bus already routes events across the mesh; stamp already produces tamper-evident hash chains. Ledger wires the two together so every event that gets recorded is both delivered live and becomes part of a permanent, independently verifiable history.

Quick Start

import { ledger } from '@manya/ledger'

const led = ledger.create({ name: 'deploys' })

ledger.onTopic(led, 'deploy.completed', (event) => {
  console.log('shipped:', event.payload)
})

ledger.record(led, 'deploy.completed', {
  sourceToolId: 'ci',
  payload: { version: '1.4.0', commit: 'abc123' },
})

ledger.verify(led)
// { valid: true, brokenAt: null, errors: [] }

If anyone tampers with a past entry, ledger.verify will report exactly where the chain breaks.

Why not just log to a file?

A log file can be edited after the fact with no trace. Each entry in a ledger chain incorporates the hash of the entry before it, so altering anything upstream breaks every hash downstream of it — the tampering is structurally detectable, not just policy-forbidden.

License

MIT