Public metadata audit

Details a trustworthy component library should publish

A trustworthy component record should make evaluation possible before source use. Look for a real preview, framework and version, dependencies, source and license treatment, accessibility and responsive notes, browser and runtime constraints, retrieval guidance, update date, support route, and known limitations. Missing or unknown fields should remain visible instead of being implied away.

Audit method

Ten exact published component records were selected from Andrew's prepared cross-family audit set. Each record is checked against the same ten public-metadata criteria. A criterion is complete only when its canonical public DTO contains the required explicit fields; absent facts remain visible as unknown and are never inferred from the preview.

Reviewed: 2026-08-26 by vro.dev catalog metadata review. Correction owner: support@vro.dev.

Fixed metadata checklist

01Real previewA published preview contract or client preview key is present.
02Framework and versionBoth framework and item version are explicit.
03DependenciesThe dependency list is explicitly published, including an empty list when applicable.
04Source and licenseSource access plus a versioned license ID, version, URL, and policy checksum are explicit.
05Accessibility notesKeyboard, reduced-motion, screen-reader, and touch notes are explicit.
06Responsive behaviorMobile support and touch behavior are explicit.
07Browser and runtimeRuntime, framework version, and at least one supported browser are explicit.
08Retrieval guidanceSource access and at least two integration or retrieval notes are explicit.
09Update dateA valid canonical update timestamp is present.
10Known limitationsAt least one item-specific constraint is published.

Dated record-level coverage

100 of 100 checked public facts were explicit. This is a coverage count, not a rating.

Ten public component records checked against ten metadata criteria.
Public record	Real preview	Framework and version	Dependencies	Source and license	Accessibility notes	Responsive behavior	Browser and runtime	Retrieval guidance	Update date	Known limitations
Signal Veil RevealEffects	Published	Published	Published	Published	Published	Published	Published	Published	Published	Published
Availability CalendarScheduling	Published	Published	Published	Published	Published	Published	Published	Published	Published	Published
Orbit Shape HeroMarketing	Published	Published	Published	Published	Published	Published	Published	Published	Published	Published
Revision Compare SliderData display	Published	Published	Published	Published	Published	Published	Published	Published	Published	Published
Research Synthesis BentoProduct interface	Published	Published	Published	Published	Published	Published	Published	Published	Published	Published
Agent Plan TreeAgent workflow	Published	Published	Published	Published	Published	Published	Published	Published	Published	Published
Signal Alert StackApplication UI	Published	Published	Published	Published	Published	Published	Published	Published	Published	Published
Paper Ink Shader HeroWebGL marketing	Published	Published	Published	Published	Published	Published	Published	Published	Published	Published
Adaptive Quote BuilderPricing	Published	Published	Published	Published	Published	Published	Published	Published	Published	Published
Afterlight Hover FooterNavigation	Published	Published	Published	Published	Published	Published	Published	Published	Published	Published

Method, limits, and corrections

This audit measures whether public decision facts are present, not whether a component is high quality, legally suitable for every project, bug-free, or compatible with every environment. It does not inspect protected source. Recheck a record after publication, archive, version, dependency, license, preview, compatibility, or metadata changes.

Public catalog · Licensed source guide · Distinctive components guide · Included Component License · Report a metadata correction