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

@berthos/audit

v0.2.4

Published

Structured audit records with a verifiable actor, a hash-chained file sink, and payload redaction

Readme

@berthos/audit

Hash-chained audit records: write them to a file, verify the chain, redact payloads, and verify attestation records.

Berth runs an AI agent's tools in a sandbox. Each tool declares what it may touch in a berth.yml manifest, and the Linux kernel enforces it.

npm install @berthos/audit

Usage

import { createFileAuditSink, readAuditFile, verifyAuditChain, agentActor } from "@berthos/audit";

const sink = createFileAuditSink({ path: "audit.jsonl" });
await sink.record({
  ts: new Date().toISOString(),
  seq: 0, // the sink assigns the real sequence number
  actor: agentActor("assistant"),
  action: "agent.tool-call",
  target: "filesystem/write_file",
  decision: "denied",
  reason: "path outside declared filesystem:write scope",
});

const result = verifyAuditChain(readAuditFile("audit.jsonl"));
console.log(result.valid ? "VALID" : `BROKEN at record ${result.brokenAt}`);

Each record commits to the one before it, so an edited record breaks the chain at that record. Someone who can rewrite the whole file can recompute the chain, so it is tamper-evident, not tamper-proof: pin the latest hash somewhere an attacker can't write if you need more.

Also exported: redact(), verifyAuditSegments() for rotated files, memory and console sinks, and verifyAttestation() for records from berth attest.

Docs

Audit reference · Attestation reference · Repo