@platformatic/undici-cache-memory
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
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.9.0 | 0 / 3 | |
| 0.8.4 | 0 / 3 | |
| 0.8.3 | 0 / 3 | |
| 0.8.2 | 0 / 2 | |
| 0.8.1 | 0 / 2 | |
| 0.8.0 | 0 / 2 | |
| 0.7.0 | 0 / 2 | |
| 0.6.0 | 0 / 2 | |
| 0.5.0 | 0 / 2 | |
| 0.4.0 | 0 / 2 | |
| 0.3.0 | 0 / 2 | |
| 0.2.0 | 0 / 2 | |
| 0.1.0 | 0 / 2 |
v0.8.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ivan-tymoshenko) than the most recent previously approved version (matteo.collina) on 2024-12-04, but ivan-tymoshenko is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.8.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (matteo.collina) than the most recent previously approved version (ivan-tymoshenko) on 2024-11-28, but matteo.collina is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.