@websolutespa/payload-utils
PayloadCms utility library of the BOM Repository
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are from the same websolutespa org; consistent with team growth, not a takeover. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 3.0.1 | 5 / 27 | |
| 3.0.0 | 5 / 27 | |
| 2.0.0 | 2 / 17 | |
| 0.0.16 | 2 / 17 | |
| 0.0.15 | 2 / 17 | |
| 0.0.14 | 2 / 17 | |
| 0.0.13 | 2 / 17 | |
| 0.0.12 | 2 / 17 | |
| 0.0.11 | 2 / 17 | |
| 0.0.10 | 2 / 17 | |
| 0.0.9 | 2 / 17 | |
| 0.0.8 | 2 / 17 | |
| 0.0.7 | 2 / 17 | |
| 0.0.6 | 2 / 17 | |
| 0.0.5 | 2 / 17 | |
| 0.0.4 | 2 / 17 | |
| 0.0.3 | 2 / 17 | |
| 0.0.2 | 1 / 15 | |
| 0.0.1 | 1 / 15 |
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.