@nx/s3-cache
A Nx plugin which provides a Nx cache which can be self hosted on Amazon 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 | missing-githead | AI (provenance): Published by GitHub Actions in the official @nx org; missing gitHead is a CI config change, not a supply-chain indicator. | ai | |
| provenance | no-provenance | AI (provenance): Published via GitHub Actions CI; provenance absence is common and no other risk signals present. | ai | |
| license | uncommon-license:Commercial | AI (license): Intentional commercial license for an official Nx paid plugin; stable across versions. | ai | |
| dependencies | unvetted-dep:@nx/key | AI (dependencies): @nx/key is an internal Nx licensing module; stable dependency for this official Nx plugin package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 5.0.7 | 9 / 0 | |
| 5.0.6 | 9 / 0 | |
| 5.0.5 | 9 / 0 | |
| 5.0.4 | 9 / 0 | |
| 5.0.3 | 9 / 0 | |
| 5.0.2 | 9 / 0 | |
| 5.0.1 | 9 / 0 | |
| 5.0.0 | 9 / 0 |
v5.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
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: GitHub Actions.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
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: GitHub Actions.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.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.