@bugsnag/plugin-electron-session
@bugsnag/electron plugin for sessions
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Scoped monorepo sub-package; sparse README and no keywords are expected for internal Bugsnag plugin packages. | ai | |
| dependencies | unvetted-dep:@bugsnag/plugin-browser-session | AI (dependencies): First-party Bugsnag dependency from the same monorepo; not a third-party risk. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 8.9.0 | 1 / 2 | |
| 8.8.0 | 1 / 2 | |
| 8.6.0 | 1 / 2 | |
| 8.4.0 | 1 / 2 | |
| 8.2.0 | 1 / 2 | |
| 8.1.1 | 1 / 2 | |
| 8.1.0 | 1 / 2 | |
| 8.0.0 | 1 / 2 |
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.