@bugsnag/delivery-node
@bugsnag/node delivery mechanism
Supply chain provenance
Status for the latest visible version.
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
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 8.10.0 | 0 / 1 | |
| 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 |
v8.10.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.