The Socket supply-chain filter (ADR-023) was added after the initial library-trace backfill, leaving the 36 traces dated 2026-05-14 without the socketRisk filter-results field the trace schema now expects. Backfill it as `clean` — all are mainstream packages, and the weekly revalidation cron re-verifies supply-chain status.
3.0 KiB
package, version, tier, decision, date, deciders, adr, filter-results, verification-commands, accepted-cves
| package | version | tier | decision | date | deciders | adr | filter-results | verification-commands | accepted-cves | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| @testing-library/react | ^16.0.0 | core | approved | 2026-05-14 |
|
null |
|
|
Filter: license
npm view @testing-library/react license returns MIT. MIT is on the allowlist.
Filter: types
@testing-library/react ships its own TypeScript declaration files. No separate @types/ package is needed.
Filter: maintenance
Actively maintained by the Testing Library organization. The 16.x line targets React 19. Regular releases; strong community and ecosystem adoption.
Filter: boundary-fit
@testing-library/react is a dependency of @repo/core-testing, the workspace's shared testing infrastructure. It provides render, screen, fireEvent, and related utilities for component tests. Feature packages that test UI components use these utilities via core-testing. This is the correct placement for shared test infrastructure.
Filter: shadow-check
@testing-library/react is the sole React component testing utility in the workspace. No competing library (Enzyme, React Test Renderer) is present.
Filter: eu-residency
@testing-library/react is a test utility library with no network communication. EU residency does not apply.
Filter: cve-scan
pnpm audit --audit-level=moderate reports no advisories against @testing-library/react at the time of this trace.
Filter: named-consumer
@repo/core-testing uses @testing-library/react to provide the render utility and screen query API for component tests. Feature packages with UI components use these via core-testing. Named, non-hypothetical consumer exists today.
Prompt: replaces
@testing-library/react replaces Enzyme and React Test Renderer. Testing Library's philosophy of testing from the user's perspective (querying by role, label, text) produces more resilient tests than implementation-detail-aware approaches.
Prompt: migration-cost-out
Hard. render, screen, fireEvent, and userEvent APIs from Testing Library are used in all component tests. Migrating to a different testing approach requires rewriting all component tests and changing the query strategy (from accessibility-tree queries to DOM selectors or component internals).
Prompt: alternatives-considered
- Enzyme — Deprecated and no longer maintained for React 18+; Testing Library is the ecosystem standard.
react-dom/test-utils— Lower-level API without the accessibility-query helpers; more verbose and less idiomatic for testing user behavior.