@electron-forge/shared-types
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI/CD publishing with SLSA attestation; expected for electron/forge. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 7.11.2 | 4 / 0 | |
| 7.11.1 | 4 / 0 | |
| 7.11.0 | 4 / 0 | |
| 7.10.2 | 4 / 0 | |
| 7.10.1 | 4 / 0 | |
| 7.10.0 | 4 / 0 | |
| 7.9.0 | 4 / 0 | |
| 7.8.3 | 4 / 0 | |
| 7.8.2 | 4 / 0 | |
| 7.8.1 | 4 / 0 | |
| 7.8.0 | 4 / 0 | |
| 7.7.0 | 4 / 0 | |
| 7.6.1 | 4 / 0 | |
| 7.6.0 | 4 / 0 | |
| 7.5.0 | 4 / 0 |
v7.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.