@websolutespa/payload-plugin-ws-contentmachine-connector
Websolute content machine connector plugin for PayloadCms
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): No code changes vs prior version; likely a CI environment change, not a supply-chain risk. | ai | |
| phantom-deps | phantom-dep:slate-react | AI (phantom-deps): slate-react is a peer/config-level dep for a Payload CMS plugin; not directly imported but legitimately declared. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.0.11 | 5 / 39 | |
| 0.0.10 | 5 / 38 | |
| 0.0.9 | 5 / 38 | |
| 0.0.8 | 5 / 38 | |
| 0.0.7 | 5 / 38 | |
| 0.0.6 | 5 / 38 | |
| 0.0.5 | 5 / 38 | |
| 0.0.4 | 5 / 38 | |
| 0.0.3 | 2 / 38 | |
| 0.0.2 | 2 / 38 | |
| 0.0.1 | 2 / 38 |
v0.0.11
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: m.fort.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: m.fort.
v0.0.7
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: m.fort.
v0.0.6
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: m.fort.