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

@holmdigital/components

v1.2.2

Published

Prescriptive, accessible React components for regulatory compliance

Downloads

401

Readme

@holmdigital/components

npm version License: MIT TypeScript Downloads

Prescriptive, accessible React components for regulatory compliance.

Why this package?

Building accessible components from scratch is hard. Ensuring they comply with EN 301 549 and national laws is even harder.

These components are Compliant by Default. They automatically handle:

  • ARIA attributes: No need to manually manage aria-expanded, aria-controls, etc.
  • Focus Management: Built-in keyboard navigation for modal traps, dropdowns, and menus.
  • Contrast: Default styles are tested against WCAG AA/AAA requirements.

Using these components significantly reduces the risk of regulatory violations in your UI.

Installation

npm install @holmdigital/components

Usage

import { Button, FormField, Heading } from '@holmdigital/components';

function App() {
  return (
    <form>
      <Heading level={1}>Contact Us</Heading>
      <FormField 
        label="Email Address" 
        type="email" 
        required 
        autoComplete="email" 
        helpText="We'll never share your email."
      />
      
      <Button variant="primary" type="submit">
        Submit
      </Button>
    </form>
  );
}

Compliance Features

  • High Contrast: Default styles meet WCAG AA requirements.
  • Keyboard Navigation: Full focus management and visible focus indicators.
  • Screen Reader Support: Correct ARIA attributes and labels built-in.

License

MIT © Holm Digital AB