@kaliber/sanity-plugin-multi-language
Document level translations.
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Org-scoped package, clean publisher history, no behavioral change in diff. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy with identical content to prior approved version, low-risk. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Conditional peer-dep installer for TypeScript; safe guard with `|| true`; stable pattern for this Sanity plugin package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 4.4.0 | 1 / 0 | |
| 4.3.0 | 1 / 0 | |
| 4.2.1 | 1 / 1 | |
| 4.2.0 | 1 / 1 | |
| 4.1.0 | 1 / 1 |
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
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 (larsvankleef) than the most recent previously approved version (daveykropf) on 2024-07-17, but larsvankleef 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.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.