← Home

@bugsnag/plugin-react

npm Repository Homepage
9
Versions
—
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

foygltomlongridgetwometresteveahmed_bugsnaggingerbenwjoshedneysb-gulshanssmartbear_devopssb_shyamnandlagishettisb-gauravasb-jigneshrsb-priyankap

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate Bugsnag org maintainer transition; publisher has clean track record on scoped packages. ai
maintainer-change maintainer-added AI (maintainer-change): Org handoff to current Bugsnag maintainers; stable across versions. ai
maintainer-change maintainer-removed AI (maintainer-change): Old maintainers dropped during legitimate org transition. ai
dependencies unvetted-dep:@bugsnag/core AI (dependencies): @bugsnag/core is a first-party Bugsnag dependency from the same monorepo; its presence is expected and stable across all versions of this plugin. ai
provenance no-provenance AI (provenance): Established Bugsnag package predating Sigstore provenance; absence is expected and not a risk signal for this package. ai

Versions (showing 9 of 9)

Version Deps Published
8.9.0 0 / 1
8.8.0 0 / 1
8.6.0 0 / 1
8.4.0 0 / 1
8.2.0 0 / 1
8.1.1 0 / 1
8.1.0 0 / 1
8.0.0 0 / 1
7.2.1 1 / 0

v8.8.0

1 finding
INFO No provenance attestation provenance

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

v8.2.0

2 findings
HIGH Publisher changed: djskinner → gingerbenw (on 2025-01-27) provenance

This version was published by a different npm account than previous versions on 2025-01-27. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v8.1.1

2 findings
HIGH Publisher changed: djskinner → gingerbenw (on 2024-10-23) provenance

This version was published by a different npm account than previous versions on 2024-10-23. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v8.1.0

2 findings
HIGH Publisher changed: djskinner → gingerbenw (on 2024-10-23) provenance

This version was published by a different npm account than previous versions on 2024-10-23. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v8.0.0

2 findings
HIGH Publisher changed: djskinner → gingerbenw (on 2024-08-29) provenance

This version was published by a different npm account than previous versions on 2024-08-29. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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