@vercel/cli-config 0.3.5

Shared core utilities for Vercel global configuration

@vercel/cli-config@0.3.5 was published on 2026-10-29. Its manifest declares 2 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @vercel/cli-config versions · Permanent reference to 0.3.5 · Latest release

Package specifications

Version0.3.5
License declarationApache-2.0
Published2026-10-29T19:38:26.071Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count2
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size143.78 KiB
Published file count17
Package typeNot declared
ES module entryNot declared
Default entrydist/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependenciesUnknown
Repository stars16466
Repository forks3881

Install @vercel/cli-config 0.3.5

npm install @vercel/cli-config@0.3.5
pnpm add @vercel/cli-config@0.3.5
yarn add @vercel/cli-config@0.3.5

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

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.

Code-Review9/10 — Found 24/26 approved changesets -- score normalized to 9
Maintained10/10 — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
License10/10 — license file detected
Security-Policy10/10 — security policy file detected
Binary-Artifacts6/10 — binaries present in source code
Packaging10/10 — packaging workflow detected
Fuzzing0/10 — project is not fuzzed
Pinned-Dependencies3/10 — dependency not pinned by hash detected -- score normalized to 3
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness