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

blocksmith-audit

v0.1.0

Published

The Blocksmith accessibility gate — real axe-core over the rendered DOM + anti-gaming structural checks + a self-contained CSP, fail-closed. A CLI, a library, and the core of an MCP conscience.

Readme

@blocksmith/audit

The accessibility gate — real axe-core (WCAG 2 A/AA + best-practice) run over the rendered DOM in headless Chrome, plus anti-gaming structural checks and a required self-contained CSP, on every page. Fail-closed. It is what makes an AI-generated site provably accessible instead of "accessible-ish": a reproducible artifact of verification, not a claim.

Unlike a PR-time scanner, it is designed to gate generation: the generator cannot self-certify past it.

CLI

blocksmith-audit ./dist                 # exit 0 if it provably passes, 1 if not
blocksmith-audit ./dist --json          # machine-readable report
blocksmith-audit ./dist --report acr    # write an Accessibility Conformance Report (acr.md + acr.json)
blocksmith-audit ./dist --grader-resolved-contrast   # treat gradient contrast axe can't compute as informational

Library

import { runAudit, conformanceReport, composeVerifiers, weightBudget } from "@blocksmith/audit";

const report = await runAudit("./dist");        // { ok, critical, serious, violations, structural, pages }
if (!report.ok) process.exit(1);

const acr = conformanceReport(report, { product: "My Site", date: "2026-07-26" });
// acr.markdown / acr.json — an honest, evidence-backed conformance report (never "compliant")

// Multi-objective: a11y is objective 1 of N.
const gate = gateWith([weightBudget(500_000)]);  // real axe AND a page-weight budget

What it checks

  • axe-core WCAG2 A/AA + best-practice over the rendered DOM (not the source).
  • Anti-gaming structural invariants: a visible-content floor (not innerText — defeats off-screen/transparent/1px filler), exactly one <h1>, a <main> landmark, decorative <canvas> aria-hidden, and text over verifiable (opaque) backgrounds.
  • Self-contained CSP: default-src 'self'|'none' with no external origins.
  • Multi-page: every .html is audited; all must pass.

Honest scope

The gate proves the machine-testable WCAG criteria (roughly the majority of real-world failures) plus the structural invariants. It does not replace human review of keyboard flow, focus order, screen-reader semantics beyond axe, reduced-motion adherence, or cognitive load. The conformance report says so explicitly.

Requirements

Node ≥ 23.6 (ships native TypeScript) and a Chrome/Chromium the audit can launch (npx playwright install chrome).