@sanity/cli-build 0.1.1

Internal Sanity package for building studios and apps

@sanity/cli-build@0.1.1 was published on 2026-05-13. Its manifest declares 1 runtime dependency and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=20.19.1 <22 || >=22.12.

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

Package specifications

Version0.1.1
License declarationMIT
Published2026-05-13T20:09:29.280Z
Node.js requirement>=20.19.1 <22 || >=22.12
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size40.56 KiB
Published file count20
Package typemodule
ES module entryNot declared
Default entry./dist/_exports/_internal.js
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies23
Repository stars1
Repository forks1

Install @sanity/cli-build 0.1.1

npm install @sanity/cli-build@0.1.1
pnpm add @sanity/cli-build@0.1.1
yarn add @sanity/cli-build@0.1.1

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