react-native-navigation
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | url-dep:github-release-notes | AI (npm-metadata): devDependency only; pinned to a specific commit tarball for release tooling, no runtime impact. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a declared runtime dependency in dependencies; phantom-dep is a false positive here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate Wix OSS package; mass-production signal from maintainer 'artald' is a false positive for this well-known package. | ai | |
| phantom-deps | phantom-dep:react-native-redash | AI (phantom-deps): Platform-specific native package; phantom-dep heuristic is unreliable for this pattern. | ai | |
| phantom-deps | phantom-dep:reanimated-color-picker | AI (phantom-deps): Referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:ssim.js | AI (phantom-deps): Referenced in config files; stable false positive for this package. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 8.8.7 | 5 / 59 | |
| 8.8.6 | 5 / 59 | |
| 8.8.5 | 5 / 59 | |
| 8.8.4 | 5 / 59 | |
| 8.8.3 | 5 / 59 | |
| 8.8.2 | 5 / 58 | |
| 8.4.3 | 8 / 55 | |
| 8.4.2 | 8 / 55 | |
| 8.4.1 | 8 / 55 | |
| 8.4.0 | 8 / 55 | |
| 8.3.2 | 8 / 55 | |
| 8.3.1 | 8 / 55 | |
| 8.3.0 | 8 / 55 | |
| 8.2.2 | 8 / 56 | |
| 8.2.1 | 8 / 56 | |
| 8.2.0 | 8 / 56 | |
| 8.1.2 | 8 / 56 | |
| 8.1.1 | 8 / 56 | |
| 8.1.0 | 8 / 56 |
v8.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.8.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.