@bugsnag/expo
Bugsnag error reporter for Expo applications
2
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
foygltomlongridgetwometresteveahmed_bugsnaggingerbenwjoshedneysb-gulshanssb-gaurava
Keywords
bugsnagexporeact nativeexceptionerrorjavascriptmonitoringreportingstabilitymobile
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:bugsnag-build-reporter | AI (dependencies): bugsnag-build-reporter is Bugsnag's own tooling; expected dependency for this SDK. | ai | |
| provenance | no-provenance | AI (provenance): Established Bugsnag org package; lack of provenance is consistent across all prior versions. | ai |
v55.0.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v54.1.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.