← Home

@bugsnag/browser

npm Repository Homepage
11
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

sb--rohandhimansb-gulshanssmartbear_devopssb_shyamnandlagishettisb-gauravasb-jigneshrsb-priyankapanshuman_singh

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Publisher matched as known maintainer; consistent with org maintainer list refresh. ai
maintainer-change maintainer-removed AI (maintainer-change): Large stable package with routine maintainer list churn, no other malicious signal. ai
publish-pattern dormant-publish AI (publish-pattern): Likely analyzer history gap, not real 7yr dormancy for an actively maintained popular package. ai
bogus-package bogus-package AI (bogus-package): Terse README/no keywords is normal for a monorepo sub-package; stable FP. ai

Versions (showing 11 of 11)

Version Deps Published
8.10.0 1 / 17
8.9.0 1 / 17
8.8.1 1 / 17
8.8.0 1 / 17
8.6.0 1 / 17
8.4.0 1 / 17
8.2.0 1 / 17
8.1.2 1 / 17
8.1.1 1 / 17
8.1.0 1 / 17
8.0.0 1 / 17

v8.10.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: sb-priyankap → sb-jigneshr (on 2026-07-10, known maintainer) provenance

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.9.0

2 findings
HIGH Publisher changed: gingerbenw → sb-priyankap (on 2026-04-08) provenance

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

LOW No provenance attestation provenance

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

v8.2.0

1 finding
LOW No provenance attestation provenance

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

v8.1.2

1 finding
LOW No provenance attestation provenance

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

v8.1.1

1 finding
LOW No provenance attestation provenance

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

v8.1.0

1 finding
LOW No provenance attestation provenance

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

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