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

@deverge/confidence

v0.1.6

Published

Confidence sidecar CLI — deterministic constitution enforcement. AI at authoring time, determinism at enforcement time.

Readme

@deverge/confidence

Deterministic constitution enforcement for AI-generated and citizen-developed code.

AI at authoring time, determinism at enforcement time. The LLM helps write the ruler; it never eyeballs the measurement. There is no LLM anywhere in this binary.

confidence runs your repo's constitution — machine-readable, owned, provenance-linked engineering standards living in .confidence/ — against a change-set, using the lint/analysis engines you already trust (ESLint, Semgrep, Larastan, Pint, Pest), and reports honestly: what was verified, what failed (with evidence), and what no rule governs at all.

Why not just CI?

Your CI could enforce your standards today. It doesn't — because lint configs have no authoring loop, no owner, no provenance, and no lifecycle. Standards live in review comments instead, applied by hand, at the most expensive moment. confidence is the pipeline that turns a repeated review comment into an owned, fixture-tested, deterministic rule — and tells you, per change, what is and is not covered.

  • No tested rule, no enforceable claim — every rule ships with failing/passing/mutation fixtures and must prove them (from randomized paths) before it may enforce. Fail closed.
  • Honest coverage — claimed per rule construct only; ungoverned changes are listed as UNCLASSIFIED — human judgment required. No scores, no percentages, no false confidence.
  • The author never controls the gate — changes are judged by the base branch's constitution; policy changes ship in CODEOWNERS-gated, constitution-only PRs.
  • Audited overrides, no bypass flag — waivers name an approver (≠ author), a reason, and an expiry, and are stamped into the replayable report artifact.
  • Blocking is earned — rules start advisory and graduate on evidence; noisy rules auto-demote. Rule failure is a product signal, never user blame.

Usage

npm i -D @deverge/confidence

npx confidence run --base origin/main --head HEAD   # PR gate: report + comment + exit code
npx confidence run --staged                          # local: ~2s, emits a commit trailer
npx confidence validate                              # meta-gate: schema + fixture proof

Exit codes: 0 clean · 1 blocking failure(s) · 2 meta-error / excluded blocking rule (fail closed). Advisory findings never affect the exit code.

Agent integration is the absence of integration: exit codes and a trailer line. No MCP server, no prompt content, zero context cost.

Status

v0.1 — working spike. Constitution schema v1 (see the spec in the source repo). ESLint adapter battle-tested; Semgrep contract-tested; Larastan/Pint/Pest adapters awaiting integration hardening against a production Laravel codebase.

License

Apache-2.0 · © 2026 Deverge