@sanity/assist
You create the instructions; Sanity AI Assist does the rest.
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are all first-party @sanity/* packages; no suspicious third-party additions. | ai | |
| provenance | missing-githead | AI (provenance): GitHub Actions publish environment may not set gitHead; SLSA attestation provides equivalent commit traceability. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are Sanity.io org members consistent with monorepo consolidation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long gap explained by major version bump (v5→v6) and CI/CD migration for official Sanity.io org package. | ai | |
| provenance | publisher-changed | AI (provenance): Sanity.io migrated publishing to GitHub Actions CI/CD; consistent with SLSA attestation and org ownership. | ai | |
| dependencies | unvetted-dep:get-random-values-esm | AI (dependencies): Standard crypto.getRandomValues ESM polyfill; appropriate for a browser-targeting Sanity plugin. | ai | |
| provenance | slsa-provenance | AI (provenance): Official Sanity.io CI/CD pipeline with Sigstore attestation; stable for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 6.0.6 | 10 / 14 | |
| 6.0.5 | 10 / 14 | |
| 6.0.4 | 10 / 13 | |
| 6.0.3 | 10 / 13 | |
| 6.0.2 | 10 / 13 | |
| 6.0.1 | 10 / 13 | |
| 6.0.0 | 10 / 13 | |
| 5.0.4 | 13 / 28 | |
| 5.0.3 | 9 / 28 | |
| 5.0.2 | 9 / 28 |
v6.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.4
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: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-03-23. 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.
v6.0.3
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: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-03-16. 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.
v6.0.2
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: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-03-10. 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.
v6.0.1
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: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-03-06. 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.
v6.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: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-03-06. 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.
v5.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.