sanity-plugin-utils
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Moved to sanity-svc.npm service account for org-level CI publishing; legitimate transition. | ai | |
| provenance | missing-githead | AI (provenance): Monorepo CI publish via pkg-utils; SLSA provenance present instead. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Added official Sanity org accounts (sanity-io, sanity-svc.npm, bjoerge). | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Major version bump after monorepo migration explains dormancy. | ai | |
| source-diff | source-size-dropped | AI (source-diff): v2 rewrite with simplified API; ships only dist/ from monorepo build. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 2.0.0 | 5 / 12 | |
| 1.8.0 | 4 / 27 | |
| 1.7.0 | 4 / 27 | |
| 1.6.8 | 4 / 27 |
v2.0.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sanity-svc.npm.
This version was published by a different npm account than previous versions on 2026-06-05. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.