@testing-library/react-native 13.2.0

Simple and complete React Native testing utilities that encourage good testing practices.

@testing-library/react-native@13.2.0 was published on 2025-03-05. Its manifest declares 4 runtime dependencies and 4 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=18.

All @testing-library/react-native versions · Permanent reference to 13.2.0 · Latest release

Package specifications

Version13.2.0
License declarationMIT
Published2025-03-05T17:05:06.803Z
Node.js requirement>=18
Type declarationsBundled declarations
Runtime dependency count4
Peer requirement count4
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size650.30 KiB
Published file count308
Package typeNot declared
ES module entryNot declared
Default entrybuild/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies19
Repository stars3427
Repository forks278

Install @testing-library/react-native 13.2.0

npm install @testing-library/react-native@13.2.0
pnpm add @testing-library/react-native@13.2.0
yarn add @testing-library/react-native@13.2.0

Runtime dependencies

Peer requirements

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Maintained10/10 — 28 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
Code-Review0/10 — Found 1/30 approved changesets -- score normalized to 0
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Binary-Artifacts10/10 — no binaries found in the repo
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies10/10 — all dependencies are pinned
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
Security-Policy0/10 — security policy file not detected
SAST8/10 — SAST tool is not run on all commits -- score normalized to 8

Evidence and freshness