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

@rgaa-source/core

v0.2.1

Published

Accessibility engine mapping axe-core and custom rules to the French RGAA 4.1 reference frame.

Readme

@rgaa-source/core

Accessibility engine: axe-core orchestration, rules of its own, WCAG ↔ RGAA 4.1.2 mapping, scoring.

Pure TypeScript, with no framework dependency and no Node API: the same engine runs under Playwright, in an extension content script, and in a unit test.

What it brings

  • RGAA mapping established per rule. Going through WCAG alone is unusable: success criterion 1.1.1 underpins nineteen RGAA criteria across seven topics on its own. The table of 106 criteria is generated from the official French government (DINUM) source, carrying the SHA-256 digest of what produced it.
  • Seven rules of its own, answering criteria axe does not test: declared language inconsistent with the content (8.4), a page title nobody wrote (8.6), missing skip link (12.7), ungrouped fields (11.5/11.6), missing autocomplete (11.13), link text that is not explicit (6.1).
  • Coverage reported on every result: how many criteria were examined, and above all how many were not.

Adding a rule

Implement AccessibilityRule, add a line to the registry. The scanner is never touched.

export const myRule: AccessibilityRule = {
  id: 'rgaa-my-rule',
  severity: 'moderate',
  wcag: ['1.3.1'],
  rgaa: ['9.3'],
  message: '…',
  help: '…',
  recommendation: '…',
  run({ document }) {
    const candidates = [...document.querySelectorAll('…')];
    return { candidates: candidates.length, findings: [] };
  },
};

candidates is the score's denominator: a rule that examined nothing neither penalises nor rewards the page. A rule marked review: true produces points to verify rather than failures, and does not enter the score.

Full documentation: project README · en français.