← Home

@bugsnag/electron

npm Repository Homepage

@bugsnag/electron notifier

7
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-gulshanssmartbear_devopssb_shyamnandlagishettisb-gauravasb-jigneshrsb-priyankap

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@bugsnag/electron-network-status AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic false positive for this monorepo package. ai
bogus-package bogus-package AI (bogus-package): Bugsnag SDK packages are minimal wrappers; sparse README and no keywords are expected for this org's packages. ai

Versions (showing 7 of 7)

Version Deps Published
8.9.0 30 / 0
8.8.1 30 / 0
8.8.0 30 / 0
8.7.0 30 / 0
8.6.0 30 / 0
8.5.0 30 / 0
8.4.0 30 / 0

v8.9.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.

v8.8.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.8.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.

v8.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.6.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.4.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.