react-native-screens
Native navigation primitives for your React Native app.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:react-native-gradle-plugin | AI (dependencies): react-native-gradle-plugin is a platform-specific Android build tool dependency; its use in react-native-screens is expected and benign for this package. | ai | |
| phantom-deps | phantom-dep:react-native-gradle-plugin | AI (phantom-deps): Declared but not directly imported because it is a platform-specific binary package for Android Gradle builds; this pattern is stable for react-native-screens. | ai | |
| source-diff | large-new-source-files | AI (source-diff): v3.28.0 added Reanimated integration (evidenced by reanimated/index paths in package.json), naturally producing many new source files. No obfuscation or malicious patterns indicated. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer tboba has clean history (115 approved, 0 rejected); legitimate transition for mature package. | ai | |
| provenance | no-provenance | AI (provenance): Provenance attestation is not yet standard practice on npm; absence is not a security signal for established packages. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): react-freeze is a legitimate Software Mansion library intentionally added to react-native-screens for React 18 concurrent feature support; not a supply chain risk. | ai | |
| provenance | missing-githead | AI (provenance): Package transitioned to GitHub Actions CI publishing; missing gitHead is explained by the changed publish environment. SLSA provenance attestation provides stronger integrity assurance. | ai | |
| publish-pattern | suspicious-version-number | AI (publish-pattern): react-native-screens uses this nightly versioning pattern (date + commit hash suffix) for automated nightly CI builds; not a malware indicator for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher transition from kacperkapusciak to tboba is legitimate; new publisher has strong track record. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall runs git submodule update and yarn install—standard monorepo setup, not arbitrary code execution. | ai | |
| dependencies | unvetted-dep:react-freeze | AI (dependencies): react-freeze is a legitimate React Native ecosystem package; its use in react-native-screens for subtree freezing is expected and stable across versions. | ai |
Versions (showing 100 of 117)
| Version | Deps | Published |
|---|---|---|
| 4.25.2 | 2 / 42 | |
| 4.25.1 | 2 / 42 | |
| 4.25.0 | 2 / 42 | |
| 4.24.0 | 2 / 41 | |
| 4.23.0 | 2 / 41 | |
| 4.22.0 | 2 / 41 | |
| 4.21.0 | 2 / 41 | |
| 4.20.0 | 2 / 41 | |
| 4.19.0 | 2 / 41 | |
| 4.18.0 | 2 / 41 | |
| 4.17.1 | 2 / 41 | |
| 4.17.0 | 2 / 41 | |
| 4.16.0 | 3 / 41 | |
| 4.15.4 | 3 / 41 | |
| 4.15.3 | 3 / 41 | |
| 4.15.2 | 3 / 41 | |
| 4.15.1 | 3 / 41 | |
| 4.15.0 | 3 / 41 | |
| 4.14.1 | 3 / 41 | |
| 4.14.0 | 3 / 41 | |
| 4.13.1 | 3 / 42 | |
| 4.13.0 | 3 / 42 | |
| 4.12.0 | 3 / 42 | |
| 4.11.1 | 3 / 42 | |
| 4.11.0 | 3 / 42 | |
| 4.10.0 | 2 / 40 | |
| 4.9.2 | 2 / 40 | |
| 4.9.1 | 2 / 40 | |
| 4.9.0 | 2 / 40 | |
| 4.8.0 | 2 / 40 | |
| 4.7.0 | 2 / 40 | |
| 4.6.0 | 2 / 40 | |
| 4.5.0 | 2 / 39 | |
| 4.4.0 | 2 / 40 | |
| 4.3.0 | 2 / 40 | |
| 4.2.0 | 2 / 40 | |
| 4.1.0 | 2 / 40 | |
| 4.0.0 | 2 / 40 | |
| 3.37.0 | 2 / 40 | |
| 3.36.0 | 2 / 40 | |
| 3.35.0 | 2 / 40 | |
| 3.34.1 | 2 / 40 | |
| 3.34.0 | 2 / 40 | |
| 3.33.0 | 2 / 40 | |
| 3.32.0 | 2 / 40 | |
| 3.31.1 | 2 / 40 | |
| 3.31.0 | 2 / 40 | |
| 3.30.1 | 2 / 40 | |
| 3.30.0 | 2 / 40 | |
| 3.29.0 | 2 / 39 | |
| 3.28.0 | 2 / 39 | |
| 3.27.0 | 2 / 39 | |
| 3.26.0 | 2 / 39 | |
| 3.25.0 | 2 / 41 | |
| 3.24.0 | 2 / 41 | |
| 3.23.0 | 2 / 41 | |
| 3.22.1 | 2 / 41 | |
| 3.22.0 | 2 / 41 | |
| 3.21.1 | 2 / 41 | |
| 3.21.0 | 2 / 41 | |
| 3.20.0 | 2 / 44 | |
| 3.19.0 | 2 / 44 | |
| 3.18.2 | 2 / 41 | |
| 3.18.1 | 2 / 41 | |
| 3.18.0 | 2 / 41 | |
| 3.17.0 | 2 / 41 | |
| 3.16.0 | 2 / 41 | |
| 3.15.0 | 2 / 41 | |
| 3.14.1 | 2 / 41 | |
| 3.14.0 | 2 / 41 | |
| 3.13.1 | 2 / 41 | |
| 3.13.0 | 2 / 41 | |
| 3.12.0 | 3 / 41 | |
| 3.11.1 | 2 / 41 | |
| 3.11.0 | 2 / 41 | |
| 3.10.2 | 2 / 41 | |
| 3.10.1 | 2 / 41 | |
| 3.10.0 | 2 / 41 | |
| 3.9.0 | 2 / 40 | |
| 3.8.0 | 1 / 40 | |
| 3.7.2 | 1 / 40 | |
| 3.7.1 | 1 / 40 | |
| 3.7.0 | 1 / 40 | |
| 3.6.0 | 1 / 39 | |
| 3.5.0 | 1 / 39 | |
| 3.4.0 | 1 / 37 | |
| 3.3.0 | 0 / 37 | |
| 3.2.0 | 0 / 37 | |
| 3.1.1 | 0 / 37 | |
| 3.1.0 | 0 / 37 | |
| 3.0.0 | 0 / 37 | |
| 2.18.1 | 0 / 37 | |
| 2.18.0 | 0 / 36 | |
| 2.17.1 | 0 / 36 | |
| 2.17.0 | 0 / 36 | |
| 2.16.1 | 0 / 36 | |
| 2.16.0 | 0 / 36 | |
| 2.15.2 | 0 / 36 | |
| 2.15.1 | 0 / 36 | |
| 2.15.0 | 0 / 36 |
v4.25.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.25.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.25.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.