@websolutespa/payload-plugin-localization
Localization 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
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 3.0.1 | 0 / 24 | |
| 3.0.0 | 0 / 24 | |
| 2.0.0 | 0 / 14 | |
| 1.7.4 | 0 / 14 | |
| 1.7.3 | 0 / 14 | |
| 1.7.2 | 0 / 14 | |
| 1.7.1 | 0 / 14 | |
| 1.7.0 | 0 / 14 | |
| 1.6.3 | 0 / 14 | |
| 1.6.2 | 0 / 14 | |
| 1.6.1 | 0 / 14 | |
| 1.6.0 | 0 / 14 |
v1.7.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 (m.fort) than the most recent previously approved version (actarian) on 2025-02-26, but m.fort 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.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.