@vercel/connect 0.2.2

SDK for obtaining scoped tokens for third-party services on behalf of apps or users. Authenticates the calling Vercel project via [`@vercel/oidc`](https://www.npmjs.com/package/@vercel/oidc) and exchanges the OIDC token for a Vercel Connect-issued credent

@vercel/connect@0.2.2 was published on 2026-06-10. Its manifest declares 1 runtime dependency and 5 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @vercel/connect versions · Permanent reference to 0.2.2 · Latest release

Package specifications

Version0.2.2
License declarationApache-2.0
Published2026-06-10T06:36:20.288Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count5
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size96.33 KiB
Published file count39
Package typemodule
ES module entryNot declared
Default entryNot declared
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies24
Repository stars16421
Repository forks3868

Install @vercel/connect 0.2.2

npm install @vercel/connect@0.2.2
pnpm add @vercel/connect@0.2.2
yarn add @vercel/connect@0.2.2

Runtime dependencies

Peer requirements

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.

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