@sanity/migrate
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/commands/migrations/create.js | AI (source-diff): SWC-compiled output with standard async/class helpers; not obfuscated, consistent with build tooling in package.json. | ai | |
| source-diff | source-size-tripled | AI (source-diff): v5→v6 major refactor; size increase consistent with added functionality, not injected payload. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Major version bump with significant feature expansion; SLSA provenance confirms CI/CD build integrity. | ai | |
| phantom-deps | phantom-dep:@sanity/eslint-config-cli | AI (phantom-deps): Same-org eslint config referenced via config files, not direct imports — expected pattern. | ai | |
| phantom-deps | phantom-dep:@sanity/cli-test | AI (phantom-deps): Same-org package used as test infrastructure; declared but not directly imported is expected. | ai | |
| phantom-deps | phantom-dep:@oclif/plugin-help | AI (phantom-deps): Referenced in oclif config (package.json plugins field), not via direct import — expected pattern. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): sanity-svc.npm is the Sanity org service account; stable maintainer transition for this package. | ai | |
| provenance | publisher-changed | AI (provenance): sanity-svc.npm is Sanity's org CI account; SLSA attestation confirms legitimate pipeline publish. | ai | |
| dependencies | unvetted-dep:@sanity/mutate | AI (dependencies): First-party Sanity dependency; consistent with package scope across versions. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 6.1.2 | 10 / 18 | |
| 6.1.1 | 10 / 18 | |
| 6.1.0 | 10 / 18 | |
| 6.0.0 | 11 / 20 | |
| 5.2.5 | 16 / 20 | |
| 5.2.4 | 17 / 19 | |
| 5.2.3 | 17 / 28 | |
| 5.2.2 | 17 / 28 | |
| 5.2.1 | 17 / 28 | |
| 5.1.0 | 9 / 10 | |
| 5.0.1 | 9 / 10 | |
| 5.0.0 | 9 / 10 | |
| 4.22.0 | 9 / 10 | |
| 4.21.1 | 9 / 10 | |
| 4.21.0 | 9 / 10 | |
| 4.20.3 | 9 / 10 | |
| 4.20.2 | 9 / 10 | |
| 4.20.1 | 9 / 10 | |
| 4.20.0 | 9 / 10 | |
| 4.19.0 | 9 / 9 | |
| 4.18.0 | 9 / 9 | |
| 4.17.0 | 9 / 9 | |
| 4.16.0 | 9 / 9 | |
| 4.15.0 | 9 / 9 | |
| 4.14.2 | 9 / 9 | |
| 4.14.1 | 9 / 9 | |
| 4.14.0 | 9 / 9 | |
| 4.13.0 | 9 / 9 |
v6.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.22.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.21.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.21.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.20.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.20.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.20.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.20.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.19.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.18.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.17.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.16.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.14.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.14.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.14.0
2 findingsThis version was published by a different npm account than previous versions on 2025-11-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.
v4.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.