@bugsnag/plugin-react-navigation-performance
BugSnag performance monitoring for @react-navigation/native
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
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 3.4.1 | 0 / 9 | |
| 3.4.0 | 0 / 9 | |
| 3.3.0 | 0 / 9 | |
| 3.2.0 | 0 / 9 | |
| 3.0.1 | 0 / 9 | |
| 3.0.0 | 0 / 9 |
v3.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.