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

@atcn/verifiers

v1.5.1

Published

Evidence checks for ATCN policies: JUnit test reports, ESLint reports, patch digests, attestations and agent traces

Readme

@atcn/verifiers

The evidence checks that ATCN policies use to decide whether paid work is accepted. A provider submits evidence (a test report, a lint report, a patch, an attestation), and a policy says which checks it must pass. These checks read the evidence; they never run the delivered code.

| Check | What it reads | What the policy can require | | --- | --- | --- | | junit_tests | A JUnit XML test report | A minimum number of tests and a pass rate | | eslint_lint | An ESLint JSON report | At most so many errors and warnings | | patch_digest | A unified diff | A minimum number of files changed | | external_attestation | A signed attestation from an independent verifier | Version 1.1.0 also checks the run and skill it cites, the evidence it cites, its expiry and key revocation; refusals carry a code. Policies pinned to 1.0.0 are unchanged. | | agent_trace | An agent trace file | That it belongs to a run the provider declared: bound by digest, using only the declared models, inside the run's time window | | usage_cost | The usage in agent traces, priced at the agreed rates | That the usage supports the amount charged, within the agreed tolerance | | witness_quorum | Witness attestations | That enough independent witnesses, on distinct verified domains, attested to the run |

npm install @atcn/verifiers

runCheck runs one policy check against submitted evidence. See examples/local-runner/src/network.ts for how clearing calls it.

test-vectors/attestations.json holds adversarial attestations (undeclared run, wrong skill, expired, future-dated, wrong subject, stripped expiry, revoked key, revocation by another signer) with the expected outcome of each; the TypeScript and Python tests replay them.

Part of ATCN. Apache-2.0.