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

@nano-ui-kit/a2ui-validator

v0.0.1

Published

A2UI validation — structural schema validation, catalog-aware validation (component props, slots, enums), and optional semantic LLM-judge scoring. Framework-agnostic; pairs with @nano-ui-kit/a2ui-utils.

Readme

@nano-ui-kit/a2ui-validator

A2UI validation — three orthogonal layers that you compose based on how much assurance you want.

| Layer | What it checks | Cost | Determinism | |---|---|---|---| | Structural (./structural) | Shape, tag registration, required fields per NanoUI A2UI schema | µs | ✅ fully deterministic | | Catalog (./catalog) | Full prop types, enum values, slot names, validation rules from per-component a2ui.json schemas | ms | ✅ fully deterministic | | Semantic (./semantic) | Intent alignment via LLM judge (dominant pattern, required capabilities, forbidden noise) | seconds, API cost | ✱ cached per rubric+input |

Install

npm install @nano-ui-kit/a2ui-validator @nano-ui-kit/a2ui-utils

Structural validation

import { validateSchema } from '@nano-ui-kit/a2ui-validator';

const messages = [
  { type: 'updateComponents', surfaceId: 'default', components: [
    { id: 'root', component: 'Card', children: ['sec'] },
    { id: 'sec',  component: 'Section', children: ['btn'] },
    { id: 'btn',  component: 'Button', text: 'Hello' },
  ]},
];

const { valid, errors } = validateSchema(messages);

Catalog-aware validation

Needs the catalog shipped in @nano-ui-kit/a2ui-corpus:

import { validateMessages } from '@nano-ui-kit/a2ui-validator/catalog';
import catalog from '@nano-ui-kit/a2ui-corpus/catalog';

const { valid, errors } = validateMessages(messages, catalog);

Catches variant="fictional" on a component whose yaml only declares [default, info, success, warning, danger], wrong slot names, missing required props — the things structural validation is too coarse to see.

Semantic validation (optional)

import { validateSemantics } from '@nano-ui-kit/a2ui-validator/semantic';

const result = await validateSemantics({
  intent: 'password reset form',
  messages,
  rubric: {
    dominantPattern: 'forms/password-reset',
    requiredCapabilities: ['email input', 'submit button'],
    forbiddenNoise: ['login flow', 'signup'],
  },
});
// → { verdict: 'aligned' | 'partial' | 'misaligned' | 'off-topic', score, rationale }

Needs ANTHROPIC_API_KEY in the environment. Judgments are cached at <cwd>/.a2ui-semantic-cache/ keyed by sha256(rubricVersion + intent + messages) — the default Haiku-4.5 rubric is ~108k tokens per 100-intent run.

Development / design notes

  • Layer 1 and 2 are framework-agnostic — they validate any A2UI message set against any component registry.
  • Layer 3 is opinionated: specific rubric, specific model. If you want a different model, provide a custom judge function to validateSemantics.
  • This package is Node-only today (fs-backed semantic cache). Browser builds of the structural/catalog layers work via standard ESM import.

License

MIT © Kim Granlund