@bugsnag/react-native
Bugsnag error reporter for React Native applications
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established Bugsnag package; no provenance is consistent across all prior versions of this monorepo. | ai | |
| dependencies | unvetted-dep:@bugsnag/plugin-network-breadcrumbs | AI (dependencies): Sibling @bugsnag/* package from same monorepo at matching version; stable pattern across all releases. | ai | |
| dependencies | unvetted-dep:@bugsnag/plugin-react-native-event-sync | AI (dependencies): Sibling @bugsnag/* package from same monorepo at matching version; stable pattern across all releases. | ai | |
| dependencies | unvetted-dep:@bugsnag/plugin-react-native-global-error-handler | AI (dependencies): Sibling @bugsnag/* package from same monorepo at matching version; stable pattern across all releases. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 8.10.0 | 12 / 3 | |
| 8.9.0 | 12 / 3 | |
| 8.8.1 | 12 / 3 | |
| 8.8.0 | 12 / 3 |
v8.10.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sb-jigneshr) than the most recent previously approved version (sb-priyankap) on 2026-07-10, but sb-jigneshr is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v8.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.