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

@chaafoo/anchored

v0.8.0

Published

anchored — the verification gate for AI work. Evidence-gated runs: no criterion reaches done without validator-authored proof, grounded in an executed command.

Readme

@chaafoo/anchored

The verification gate for AI work. Nothing reaches done without validator-authored evidence, grounded in an executed command.

This package is the anchored CLI and core — the run-file schema, the evidence invariant, the atomic store, and the nine flat verbs. It is what enforces the guarantee; it does not orchestrate anything and it never calls an AI.

Most people don't install this directly. It ships inside the anchored plugin for Claude Code, which puts the binary on PATH and adds the /a:run and /a:setup skills plus the validator agent.

Install

npm install -g @chaafoo/anchored

The nine verbs

anchored anchor <slug>              # freeze a plan + its criteria into .claude/anchored/<slug>.yml
anchored claim <slug> <text>        # append a work note to the trail
anchored amend <slug>               # the only way criteria change (supersede / reject / add)
anchored validate <slug> --gate <g> # the validation packet for ONE validator spawn
anchored evidence <slug> <cN> …     # VALIDATOR-ONLY: flip to done with grounded proof
anchored fail <slug> <cN> …         # VALIDATOR-ONLY: reject with a reasoned verdict
anchored set <slug> <cN> <f> <v>    # write a declared custom field
anchored status [slug]              # the run, or summaries of every run
anchored close <slug>               # refused while any active criterion is unproven

Every call prints one JSON envelope: { ok, command, result | error }.

The invariant

A criterion reaches done only with evidence: {by: validator, snapshot, grounded, at}, parsed fail-closed on every write. grounded is executed-command output. A prose verdict proves a criterion only where its author declared judgment: true up front — the one opt-out, visible in the run file. failed requires a reasoned verdict, close stays shut until every active criterion is done, and criteria are never deleted.

The engine is deterministic; the validator is an effect the skill triggers. The CLI never spawns an agent.

Docs

Full documentation, the run-file format and the plugin live at https://github.com/chafoo/anchored.

MIT © anchored contributors