@payloadcms/storage-s3
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Official PayloadCMS org package; provenance absence is consistent across all their releases. | ai | |
| dependencies | unvetted-dep:@payloadcms/plugin-cloud-storage | AI (dependencies): Same-org sibling dependency pinned to identical version; not an independent risk. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 3.85.0 | 4 / 2 | |
| 3.84.1 | 4 / 2 | |
| 3.84.0 | 4 / 2 | |
| 3.82.0 | 4 / 2 | |
| 3.81.0 | 4 / 2 | |
| 3.80.0 | 4 / 2 | |
| 3.79.1 | 4 / 2 | |
| 3.79.0 | 4 / 2 | |
| 3.78.0 | 4 / 2 |
v3.85.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.84.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.84.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.82.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-08. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.81.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.
v3.80.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.79.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.79.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.
v3.78.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.