@bugsnag/plugin-server-session
@bugsnag/js plugin to enable session tracking in server applications
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Provenance is absent on ~88% of npm; not a disqualifier for established packages. | ai | |
| dependencies | unvetted-dep:backo | AI (dependencies): backo is a well-known, stable exponential backoff utility; appropriate for session retry logic in this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped Bugsnag plugin; sparse README/keywords are typical for internal monorepo packages. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 8.9.0 | 1 / 1 | |
| 8.8.0 | 1 / 1 | |
| 8.6.0 | 1 / 1 | |
| 8.4.0 | 1 / 1 | |
| 8.2.0 | 1 / 1 | |
| 8.1.1 | 1 / 1 | |
| 8.1.0 | 1 / 1 | |
| 8.0.0 | 1 / 1 |
v8.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.