← Home

@bugsnag/cli

npm Repository Homepage
12
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 — 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
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 12 of 12)

Version Deps Published
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.3.1 1 / 2
3.3.0 1 / 2
3.2.0 1 / 2
3.1.1 1 / 2
3.0.1 1 / 0

v3.10.1

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node postinstall.js

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.

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

v3.3.1

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.

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

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

v3.1.1

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.

v3.0.1

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.