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

@a11yci/diff

v0.5.0

Published

Regression diff for accessibility audits: what issues did this change add, fix, or leave unchanged.

Downloads

553

Readme

@a11yci/diff

Regression-only diff for accessibility audits. Given two AuditResults (base and head), returns { added, fixed, unchanged } so CI gates only on the issues a change introduces — not the pre-existing backlog. Normalizes volatile framework class hashes so cosmetic churn isn't reported as a new issue.

Identity is per node, by content fingerprint, not by selector. axe reports one issue per rule per page and its generated selector latches onto the volatile Emotion/MUI css-XXXX class, so a selector-based comparison is blind to a same-count swap (a removed offending node replaced by a different one). Instead the engine fingerprints each node by stable content (tag, role, accessible name, and rule-specific data such as a contrast color pair), and the diff compares the multisets of those fingerprints per rule. So it catches new rules, higher counts, and swaps, while still absorbing framework-hash churn. A head fingerprint base did not have surfaces as an added entry marked change: 'worsened' (or 'new' for a wholly new rule), with addedInstances set; fewer instances is a partial fix and is never gated. When an issue carries no nodes (older JSON), it falls back to the normalized selector repeated by instanceCount.

Residual limit: two controls with identical content fingerprints are indistinguishable, so swapping one identical-looking control for another reads as unchanged.

import { diff, gatingRegressions } from '@a11yci/diff';

const d = diff(baseResult, headResult);
const blockers = gatingRegressions(d, 'fail'); // new fails only

Part of a11y-ci. Source-available under the Elastic License 2.0 (see LICENSE).