@sanity/runtime-cli
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@sanity-labs/design-tokens | AI (dependencies): Same-org alpha package used for CSS design tokens; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@sanity-labs/design-tokens | AI (phantom-deps): Used only in build scripts to copy CSS assets, not imported in source code; phantom-dep is expected. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with org-level team restructuring, not a hostile takeover. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @inquirer/prompts is a well-known official replacement for inquirer; @sanity/blueprints is first-party. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): 337-day gap aligns with large version jump (11.x to 13.x); internal product evolution, not suspicious reactivation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Sanity org internal team rotation; publisher account has strong approval track record. | ai | |
| source-diff | encoded-string-file:dist/server/static/vendor/vendor.bundle.js | AI (source-diff): Encoded strings are CodeMirror bidi algorithm lookup tables, not obfuscated payloads; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@oclif/plugin-help | AI (phantom-deps): @oclif/plugin-help is declared in oclif config plugins array, not imported directly — stable false positive for this package. | ai |
Versions (showing 75 of 75)
| Version | Deps | Published |
|---|---|---|
| 15.1.3 | 23 / 26 | |
| 15.1.2 | 23 / 26 | |
| 15.1.1 | 23 / 26 | |
| 15.1.0 | 23 / 26 | |
| 15.0.5 | 22 / 26 | |
| 15.0.4 | 22 / 26 | |
| 15.0.3 | 22 / 26 | |
| 15.0.2 | 22 / 26 | |
| 15.0.1 | 22 / 26 | |
| 15.0.0 | 22 / 26 | |
| 14.13.4 | 22 / 26 | |
| 14.13.3 | 22 / 26 | |
| 14.13.2 | 22 / 26 | |
| 14.13.1 | 22 / 26 | |
| 14.13.0 | 22 / 25 | |
| 14.12.1 | 22 / 25 | |
| 14.12.0 | 22 / 25 | |
| 14.11.0 | 22 / 25 | |
| 14.10.1 | 22 / 25 | |
| 14.10.0 | 22 / 25 | |
| 14.9.0 | 22 / 25 | |
| 14.8.6 | 22 / 25 | |
| 14.8.5 | 22 / 25 | |
| 14.8.4 | 22 / 25 | |
| 14.8.3 | 22 / 25 | |
| 14.8.2 | 22 / 25 | |
| 14.8.1 | 22 / 25 | |
| 14.8.0 | 22 / 25 | |
| 14.7.2 | 22 / 25 | |
| 14.7.1 | 22 / 25 | |
| 14.7.0 | 22 / 25 | |
| 14.6.1 | 22 / 25 | |
| 14.6.0 | 22 / 25 | |
| 14.5.1 | 22 / 25 | |
| 14.5.0 | 22 / 25 | |
| 14.4.0 | 22 / 25 | |
| 14.3.0 | 22 / 25 | |
| 14.2.0 | 23 / 25 | |
| 14.1.3 | 23 / 25 | |
| 14.1.2 | 23 / 25 | |
| 14.1.1 | 23 / 25 | |
| 14.1.0 | 23 / 25 | |
| 14.0.1 | 23 / 25 | |
| 14.0.0 | 23 / 25 | |
| 13.4.1 | 23 / 25 | |
| 13.4.0 | 23 / 25 | |
| 13.3.2 | 23 / 25 | |
| 13.3.1 | 23 / 25 | |
| 13.3.0 | 23 / 25 | |
| 13.2.3 | 23 / 25 | |
| 13.2.2 | 23 / 25 | |
| 13.2.1 | 24 / 25 | |
| 13.2.0 | 24 / 25 | |
| 13.1.0 | 24 / 25 | |
| 13.0.3 | 25 / 25 | |
| 13.0.2 | 25 / 25 | |
| 13.0.1 | 25 / 25 | |
| 13.0.0 | 25 / 25 | |
| 12.4.0 | 25 / 25 | |
| 12.3.0 | 25 / 25 | |
| 12.2.0 | 25 / 25 | |
| 12.1.0 | 24 / 26 | |
| 12.0.1 | 24 / 26 | |
| 12.0.0 | 24 / 26 | |
| 11.2.6 | 23 / 26 | |
| 11.2.5 | 23 / 26 | |
| 11.2.4 | 23 / 26 | |
| 11.2.1 | 23 / 26 | |
| 11.2.0 | 23 / 26 | |
| 11.1.5 | 23 / 26 | |
| 11.1.4 | 23 / 26 | |
| 11.1.3 | 23 / 26 | |
| 11.1.2 | 23 / 26 | |
| 11.1.1 | 23 / 26 | |
| 11.1.0 | 23 / 26 |
v15.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.13.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.1
2 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.0
2 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.6
2 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.5
2 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.4
2 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.1
2 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.0
2 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.5
2 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.