@bugsnag/core
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @bugsnag/core is a legitimate, 8-year-old Bugsnag SDK package. The 1-edit similarity to 'cors' is purely coincidental; no typosquat risk exists for this scoped package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 8.9.0 | 5 / 0 | |
| 8.8.0 | 5 / 0 | |
| 8.6.0 | 5 / 0 | |
| 8.4.0 | 5 / 0 | |
| 8.2.0 | 5 / 0 | |
| 8.1.1 | 5 / 0 | |
| 8.1.0 | 5 / 0 | |
| 8.0.0 | 5 / 0 |
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.