← Home

@bugsnag/cli

npm Repository Homepage
18
Versions
—
License
Yes
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-gulshanssmartbear_devopssb_shyamnandlagishettisb-gauravasb-jigneshrsb-priyankapsb-sachinpanshuman_singh

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-removed AI (maintainer-change): Routine maintainer rotation within BugSnag org; no hostile takeover indicators. ai
semgrep semgrep:child-process-import AI (semgrep): CLI wrapper package; child_process is used to exec the downloaded bugsnag-cli binary — expected and documented pattern. ai
publish-pattern dormant-publish AI (publish-pattern): BugSnag is a known commercial vendor; gaps in CLI tool releases are normal for commercial software. No material changes in deps/scripts vs prior approved version. ai
install-scripts install-script:postinstall AI (install-scripts): @bugsnag/cli uses postinstall to fetch platform-specific prebuilt binaries — a documented, stable pattern for this CLI tool across all 49 versions. ai
typosquat typosquat.levenshtein:joi AI (typosquat): False positive: @bugsnag/cli is a scoped package under the official BugSnag namespace, not a typosquat of 'joi'. The Levenshtein match is not meaningful here. ai

Versions (showing 18 of 18)

Version Deps Published
3.10.3 2 / 2
3.10.2 2 / 2
3.10.1 2 / 2
3.10.0 2 / 2
3.9.0 2 / 2
3.8.0 2 / 2
3.6.1 2 / 2
3.6.0 2 / 2
3.5.1 1 / 2
3.5.0 1 / 2
3.3.2 1 / 2
3.3.1 1 / 2
3.3.0 1 / 2
3.2.1 1 / 2
3.2.0 1 / 2
3.1.1 1 / 2
3.1.0 1 / 2
3.0.1 1 / 0

v3.10.3

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-gulshans → sb-jigneshr (on 2026-06-23, known maintainer) provenance

This version was published by a different npm account (sb-jigneshr) than the most recent previously approved version (sb-gulshans) on 2026-06-23, 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.

v3.5.0

1 finding
LOW No provenance attestation provenance

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