Component Audits

To audit a component, open its Actions menu, choose Copy audit prompt, run the prompt against the component in the repository, then record and publish the completed result to the central audit ledger(opens in new tab). This page automatically shows recorded scores and evidence; components without a recorded result remain TBD.How components are graded, and how to get one audited(opens in new tab)

Last updated 2026-08-17

Audited14.3%17 of 119 components

Average score76.3Across 17 scored components

Component	Grade	Score	Weakest rubric area	Last audited
AlertDialogcore	B	89.6	§3 Public API contract (4/5)	2026-08-11rubric v1.2.1
AppShellcore	B	88.0	§5a Design conventions — objective (4/5)	2026-08-12rubric v1.3
AspectRatiocore	C	83.9	§4 Behavior correctness & states (3/5)	2026-08-13rubric v1.4
Avatarcore	C	78.4	§1 Accessibility & operable paths (2.5/5)	2026-08-14rubric v1.4
AvatarGroupcore	D	66.2	§1 Accessibility & operable paths (2.5/5)	2026-08-15rubric v1.4
Badgecore	C	74.2	§5a Design conventions — objective (2/5)	2026-08-10rubric v1.1
Bannercore	C	82.6	§1 Accessibility & operable paths (3/5)	2026-08-16rubric v1.4
Blockquotecore	C	79.7	§8 Docs, Storybook & docsite (3/5)	2026-08-17rubric v1.4
BottomSheetcore	TBD	—	—	never
Breadcrumbscore	TBD	—	—	never
Buttoncore	D	62.6	§5a Design conventions — objective (2/5)	2026-08-10rubric v1.1
ButtonGroupcore	TBD	—	—	never
Calendarcore	TBD	—	—	never
Cardcore	TBD	—	—	never
Carouselcore	TBD	—	—	never
Centercore	TBD	—	—	never
Chartlab	TBD	—	—	never
Chatcore	TBD	—	—	never
Chatlab	TBD	—	—	never
ChatReasoninglab	TBD	—	—	never
CheckboxInputcore	TBD	—	—	never
CheckboxListcore	TBD	—	—	never
CircularProgresslab	TBD	—	—	never
Citationcore	TBD	—	—	never
ClickableCardcore	TBD	—	—	never
Codecore	TBD	—	—	never
CodeBlockcore	TBD	—	—	never
CodeEditorlab	TBD	—	—	never
Collapsiblecore	TBD	—	—	never
CommandPalettecore	TBD	—	—	never
ComplexSelectorcore	TBD	—	—	never
ContextMenucore	TBD	—	—	never
DateInputcore	TBD	—	—	never
DateRangeInputcore	TBD	—	—	never
DateTimeInputcore	TBD	—	—	never
Dialogcore	TBD	—	—	never
Dividercore	TBD	—	—	never
Drawerlab	TBD	—	—	never
DropdownMenucore	TBD	—	—	never
EmptyStatecore	TBD	—	—	never
Fieldcore	TBD	—	—	never
FieldStatuscore	TBD	—	—	never
FileInputcore	TBD	—	—	never
FormLayoutcore	TBD	—	—	never
Gridcore	TBD	—	—	never
Headingcore	TBD	—	—	never
HoverCardcore	TBD	—	—	never
HStackcore	TBD	—	—	never
Iconcore	TBD	—	—	never
IconButtoncore	TBD	—	—	never
Indicatorcore	B	87.1	§2 Theming & token integrity (4/5)	2026-08-12rubric v1.4
InfoTiplab	TBD	—	—	never
InputGroupcore	TBD	—	—	never
Itemcore	TBD	—	—	never
Kbdcore	TBD	—	—	never
Layercore	TBD	—	—	never
Layoutcore	TBD	—	—	never
Lightboxcore	TBD	—	—	never
Linkcore	TBD	—	—	never
Listcore	TBD	—	—	never
ListInputlab	C	77.2	§9 i18n & RTL (2.5/5)	2026-08-12rubric v1.3
LogStreamlab	TBD	—	—	never
Markdowncore	TBD	—	—	never
MetadataListcore	TBD	—	—	never
MobileNavcore	TBD	—	—	never
MoreMenucore	TBD	—	—	never
MultiSelectorcore	TBD	—	—	never
NavIconcore	TBD	—	—	never
NavMenucore	TBD	—	—	never
NumberInputcore	TBD	—	—	never
Outlinecore	TBD	—	—	never
OverflowListcore	TBD	—	—	never
Overlaycore	TBD	—	—	never
Paginationcore	TBD	—	—	never
Popovercore	TBD	—	—	never
PowerSearchcore	TBD	—	—	never
ProgressBarcore	TBD	—	—	never
Radiallab	TBD	—	—	never
RadioListcore	TBD	—	—	never
Resizablecore	TBD	—	—	never
RichTextEditorrichtext	D	62.3	§9 i18n & RTL (1.5/5)	2026-08-17rubric v1.4
Sankeylab	TBD	—	—	never
Schedulelab	TBD	—	—	never
Sectioncore	TBD	—	—	never
SegmentedControlcore	TBD	—	—	never
SelectableCardcore	TBD	—	—	never
Selectorcore	TBD	—	—	never
SideNavcore	C	79.1	§5a Design conventions — objective (3/5)	2026-08-11rubric v1.2
Skeletoncore	TBD	—	—	never
Slidercore	TBD	—	—	never
Spinnercore	TBD	—	—	never
Stackcore	TBD	—	—	never
Statlab	TBD	—	—	never
StatusDotcore	TBD	—	—	never
Stepperlab	B	88.3	§1 Accessibility & operable paths (4/5)	2026-08-11rubric v1.2.1
SVGIconlab	TBD	—	—	never
Switchcore	TBD	—	—	never
Tablecore	TBD	—	—	never
TabListcore	TBD	—	—	never
Textcore	TBD	—	—	never
TextAreacore	TBD	—	—	never
TextInputcore	C	70.7	§5a Design conventions — objective (2/5)	2026-08-10rubric v1.1
ThreeDlab	TBD	—	—	never
Thumbnailcore	TBD	—	—	never
TimeInputcore	TBD	—	—	never
Timestampcore	TBD	—	—	never
Toastcore	TBD	—	—	never
ToggleButtoncore	TBD	—	—	never
Tokencore	TBD	—	—	never
Tokenizercore	TBD	—	—	never
Toolbarcore	TBD	—	—	never
Tooltipcore	F	51.3	§5a Design conventions — objective (4/5)	2026-08-10rubric v1.1
TopNavcore	TBD	—	—	never
Tourlab	TBD	—	—	never
TransferListlab	C	75.9	§9 i18n & RTL (2/5)	2026-08-12rubric v1.3
TreeListcore	TBD	—	—	never
Typeaheadcore	TBD	—	—	never
VisuallyHiddencore	TBD	—	—	never
VStackcore	TBD	—	—	never

Caveats on the recorded rows

All five rows come from the same calibration exercise on commit `dccdabea0b`, run by five independent graders. They are the only audits that exist so far, and they are honest about their limits rather than tidy.`score` is the round-2 total under rubric **v1.1** with §5 excluded and its weight redistributed — the figure the calibration record itself publishes. It was produced from **static evidence only**: no lint, test, build, axe or RTL run.The §5a/§5b numbers come from a later pass over 256 rendered screenshots at the same commit. That pass produced a single §5 grade (it predates the v1.2 split), so the same number is recorded on both halves. Those points are **not** folded into `score`: recomputing the total would need the per-section scores the calibration record never published.`blocks.count` **is** the union of both passes. Every other section reads `unpublished`: it was audited and is inside `score`, but the record published only the total. That is not `not_measured` — somebody did look — and inventing the split would be fabrication.`distinct_defects` is the record's own count; only Badge's (14) is a deduplicated figure, the rest are its approximations.Most BLOCKs here have no issue filed yet. Two link pre-existing issues. Filing the rest is the next step, not a completed one.Treat every row as a floor to re-audit under v1.2 with the tooling actually run, not as a settled grade.