← Home

@bugsnag/node

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

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): Known-maintainer manual publish per provenance note; routine org reshuffle for this trusted package. ai
publish-pattern dormant-publish AI (publish-pattern): Long-lived monorepo package with steady inbound edges; dormancy flag is a metadata artifact, not takeover evidence here. ai
typosquat typosquat.levenshtein:zod AI (typosquat): @bugsnag/node is a legitimate Bugsnag SDK package with no relation to 'zod'; the Levenshtein match is a superficial false positive that will never represent a real typosquat risk for this scoped package. ai

Versions (showing 9 of 9)

Version Deps Published
8.10.0 6 / 13
8.9.0 6 / 13
8.8.0 6 / 13
8.6.0 6 / 13
8.4.0 6 / 13
8.2.0 6 / 13
8.1.1 6 / 13
8.1.0 6 / 13
8.0.0 6 / 13

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