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

evidence-anchors

v0.13.0

Published

Deterministic checker for Evidence Anchors — machine-verifiable claims about a codebase in design docs, RFCs, and agent-written proposals. Unscoped alias of @nullius-inverba/claims.

Readme

evidence-anchors

Unscoped alias of @nullius-inverba/claims. Same checker, same version, named after the thing it checks rather than after a Latin motto.

npx evidence-anchors check "docs/rfcs/**/*.md"
npx evidence-anchors demo

Everything else — the CLI flags, the config file, the library API, the verdicts — is documented in the canonical package and the Evidence Anchors spec.

Which one should I install?

Either. They resolve to the same code, and the version numbers move together.

  • evidence-anchors — reads better in a package.json for people who have never heard of the Royal Society. The binary is evidence-anchors.
  • @nullius-inverba/claims — the canonical package, and the one the rest of the @nullius-inverba/* family (the specs, the Action, the Claude Code plugin) refers to. The binary is nullius.

If you are adding this to a shared repo where the convention matters more than the tool, prefer evidence-anchors: the name tells a reviewer what the dependency is for.

Library use

import { parseClaims, checkClaims, isFailure } from "evidence-anchors";

The full API surface is re-exported unchanged.

License

MIT © Arman Fatemi