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

@ariada-org/figma-plugin

v0.1.0

Published

Figma plugin for local Ariada design accessibility checks.

Readme

Ariada Figma Plugin

Local Figma plugin for design-time Ariada accessibility checks. It scans the current Figma selection and reports design-mappable issues for contrast, target size, text alternatives, and semantic layer metadata before a design becomes code.

Development Loading

  1. Run pnpm --filter @ariada-org/figma-plugin build.
  2. Open Figma desktop.
  3. Use Plugins > Development > Import plugin from manifest....
  4. Select packages/ariada-figma-plugin/manifest.json.
  5. Select a frame or component and run Ariada Accessibility Scan.

The manifest points to dist/code.js, so build before loading. The UI file is loaded from src/ui.html for local development.

Usage

The plugin scans selected nodes only. It recursively walks children and reports:

  • Low text contrast against the nearest solid background.
  • Interactive targets below 24 px minimum or below the 44 px preferred touch target.
  • Image-like nodes without alt, aria-label, or description plugin data, unless decorative=true.
  • Generic landmark or heading metadata that would make handoff semantics weaker.

The supported plugin data keys are role, alt, aria-label, description, decorative, and headingLevel.

Limitations

  • No network calls are made; the manifest declares networkAccess.allowedDomains: ["none"].
  • Figma layer data is not a browser DOM. This plugin does not replace runtime Ariada scans of implemented pages.
  • Background detection uses the nearest solid fill. Blends, images, gradients, effects, and token inheritance need later expansion.
  • Figma Community publishing is blocked until the founder uses the Ariada-owned Figma account to create the listing and complete marketplace review.

Evidence

Run the local harness:

pnpm --filter @ariada-org/figma-plugin test:e2e
pnpm --filter @ariada-org/figma-plugin validate:evidence

The harness scans tests/fixtures/known-bad-frame.json and writes:

  • test-report/result.html
  • scan-evidence/result.html
  • scan-evidence/result.json
  • scan-evidence/run-output.txt

Update:

  • Author: Alexander Brichkin (Agonist Development AB)
  • Date: 2026-07-01