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/lint

v0.5.0

Published

Authoring-time accessibility linter: catch a11y anti-patterns in JSX/TSX and HTML source before they render.

Readme

@a11yci/lint

The authoring-time layer of a11y-ci. It reads your source (JSX/TSX and HTML) and flags accessibility anti-patterns before anything renders, so they're caught in the editor or pre-commit instead of in a rendered CI run.

It uses real parsers, never regex: parse5 for HTML, the TypeScript compiler for JSX/TSX. That's what keeps the false-positive rate low. It only reports what it can confidently determine from the markup, and leaves contrast and computed-role checks to the rendered @a11yci/core engine.

import { lintPaths, lintSource } from '@a11yci/lint';

const findings = lintPaths(['src']);            // walk a directory
const inline = lintSource('<img src="a.png">', 'a.html'); // one snippet

Rules

| Rule | Severity | WCAG | Catches | | --- | --- | --- | --- | | img-alt | error | 1.1.1 | <img> with no alt (and not marked decorative) | | interactive-name | error | 4.1.2 | <button> / <a href> with no text or accessible name | | clickable-noninteractive | warn | 2.1.1 | <div>/<span> with onClick but no role, tabindex, or key handler | | input-label | warn | 1.3.1 | form control with no id, no aria-label, and not wrapped in a <label> | | positive-tabindex | warn | 2.4.3 | tabindex greater than 0 | | vague-link-text | warn | 2.4.4 | link text like "click here" / "read more" | | html-lang | error | 3.1.1 | <html> with no lang | | no-autofocus | info | 3.2.1 | autofocus (moves focus on load) | | obsolete-element | error | 2.2.2 | <marquee> / <blink> |

Conservative by design: a dynamic attribute (alt={x}, id={...}) or an ambiguous child suppresses the related rule rather than guessing.

CLI

npx a11y-ci lint src
npx a11y-ci lint src --format json
npx a11y-ci lint src --fail-on warn   # exit non-zero on warn-or-worse

Source-available under the Elastic License 2.0 (see LICENSE): free to use and self-host, not to resell as a hosted service.