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

@binclusive/a11y-contract

v0.6.0

Published

The public accessibility finding contract — a zod schema (type + wire parser) shared by the Binclusive OSS engine and platform.

Readme

@binclusive/a11y-contract

The public accessibility finding contract: one zod schema that is both the type and the wire parser. The OSS engine (@binclusive/a11y) emits findings against it; the private platform (auditer + kontrol) parses them against the same schema. Single-sourcing the contract in one published package keeps both sides from forking it.

The shape

A Finding is a zod discriminated union on provenance:

  • deterministic — an automated rule engine surfaced it. Lean base metadata plus the corpus tier the rule belongs to.
  • agent — the agentic tester judged it. Carries a rationale and an optional natural-language suggestion; no corpus tier.

Both arms share the metadata aligned to the persisted agentic_finding model: criterion (WCAG SC), severity, element (a DOM locator, never source), evidence, and the declared scan scope.

Metadata-only by construction

Every object is .strict(), so the schema is a closed allowlist with no field capable of carrying customer source, and no unknown key can be smuggled in — a payload bearing a source snippet fails the parse. This is the zero-data-retention guarantee made structural, not promised in prose.

Usage

import { parseFindingPayload } from "@binclusive/a11y-contract";

// Parse untrusted input at the trust boundary (throws ZodError on any violation).
const payload = parseFindingPayload(await request.json());
for (const finding of payload.findings) {
  if (finding.provenance === "agent") console.log(finding.rationale);
}