@sanity/cli 0.102.5-next

Sanity CLI tool for managing Sanity installations, managing plugins, schemas and datasets

@sanity/cli@0.102.5-next was published on 2017-03-01. Its manifest declares 33 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=4.0.0.

All @sanity/cli versions · Permanent reference to 0.102.5-next · View npm registry JSON · Latest release

Package specifications

Version0.102.5-next
License declarationMIT
Published2017-03-01T23:39:05.474Z
Node.js requirement>=4.0.0
Type declarationsNot declared
Runtime dependency count33
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entrylib/cli.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies242
Repository stars1
Repository forks1

Install @sanity/cli 0.102.5-next

npm install @sanity/cli@0.102.5-next
pnpm add @sanity/cli@0.102.5-next
yarn add @sanity/cli@0.102.5-next

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Maintained10/10 — 30 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
Code-Review9/10 — Found 23/24 approved changesets -- score normalized to 9
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow0/10 — dangerous workflow patterns detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies5/10 — dependency not pinned by hash detected -- score normalized to 5
License10/10 — license file detected
Branch-Protection4/10 — branch protection is not maximal on development and all release branches
Security-Policy10/10 — security policy file detected
Fuzzing0/10 — project is not fuzzed
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness