# Install vercel with Homebrew Cask

Command-line interface for Vercel. Version 65.9.0 via Homebrew Cask; verified from local package data.

## Install

```sh
sudo av install cask:vercel
```

Additional install commands:

### macOS

- Homebrew Cask (100%):

```sh
brew install --cask vercel
```

  Evidence: local Homebrew cask metadata

## Package facts

- **Package key:** cask:vercel
- **Package manager:** Homebrew Cask
- **Package manager page:** <https://formulae.brew.sh/cask/vercel>
- **Version:** 65.9.0
- **Source summary:** Command-line interface for Vercel
- **Homepage:** <https://vercel.com/docs/cli>
- **Upstream docs:** <https://vercel.com/docs/cli>
- **Source archive:** <https://registry.npmjs.org/@vercel/vc-native-darwin-arm64/-/vc-native-darwin-arm64-65.9.0.tgz>
- **Generated:** 2026-11-04T12:20:42+00:00

## Executables

- vercel (binary)
- vercel (binary)

## Install behavior

- Post-install hook: not defined
- Bottle: not available

## Freshness

- Page generated: 2026-11-04
- Package-manager version: 65.9.0
- Local data: ok
- Upstream repository: https://vercel.com/docs/cli
- info: No package-manager update timestamp was available.
- info: Release/tag comparison is only available for GitHub repositories.
## Project history and usage

Vercel CLI is the command-line client for deploying, developing, linking, inspecting, and operating projects on Vercel. The `vercel` and `vc` executables expose both interactive developer workflows and token-based automation for CI/CD.

### Project history

The official repository dates to 2016 and grew into a large TypeScript-centered monorepo for Vercel's CLI, builders, runtimes, and related packages. The regular CLI continues to be distributed as the `vercel` npm package, with separate native CLI binaries offered as an explicit alternative.

### Adoption history

The CLI evolved with Vercel's deployment platform: version 24 in 2022 stabilized `vercel dev` and moved most CLI code to TypeScript; version 28 added deeper Git metadata and project-linking workflows. Later releases added a device-flow login, direct API access, agent-oriented historical logs, and local-directory scoping.

### How it is used

Developers use `vercel` to deploy the current project, `vercel dev` to emulate the platform locally, and `vercel link` or `.vercel/project.json` to bind a directory to a remote project. Operational commands cover domains, DNS, environment variables, logs, deployments, rollbacks, integrations, and authenticated API requests.

### Why package nerds care

Vercel CLI is a prominent npm-installed cloud CLI whose long-running command surface tracks the shift from simple frontend deployment toward a broad programmable platform. Package users care about its dual `vercel`/`vc` commands, project-local state, cross-platform XDG-derived global state, rapid release cadence, and growing native-binary option.

### Timeline

- 2016: Official repository established.
- 2022-02-17: Vercel CLI v24 released; `vercel dev` became stable.
- 2022-08-12: Vercel CLI v28 released with expanded Git and linking behavior.
- 2025-09-12: OAuth 2.0 Device Flow became the CLI login path.
- 2026-01-27: `vercel api` added direct authenticated API access.
- 2026-02-10: `vercel logs` gained historical, agent-oriented querying.

### Related projects

- The repository also contains Vercel builders, runtimes, and platform packages; the CLI works closely with Git providers, the Vercel REST API, framework build outputs, and the separately distributed `@vercel/vc-native` binaries.

### Sources

- <https://github.com/vercel/vercel>
- <https://vercel.com/changelog/introducing-the-vercel-api-cli-command>
- <https://vercel.com/changelog/new-vercel-cli-login-flow>
- <https://vercel.com/changelog/vercel-cli-v24>
- <https://vercel.com/changelog/vercel-cli-v28>
- <https://vercel.com/docs/cli>


## Security Notes

No matching local secret-handling manifest was found for vercel. Package metadata is still published here so future coverage has a stable package URL.



## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Linux: ~/.local/share/com.vercel.cli/config.json
- macOS: ~/Library/Application Support/com.vercel.cli/config.json
- Windows: %APPDATA%\Roaming\xdg.data\com.vercel.cli\config.json

## Credential files

- Linux: ~/.local/share/com.vercel.cli/auth.json
- macOS: ~/Library/Application Support/com.vercel.cli/auth.json
- Windows: %APPDATA%\Roaming\xdg.data\com.vercel.cli\auth.json
## Source Database Details

- **Source Database:** Homebrew cask API
- **Tap:** homebrew/cask
- **Full Token:** vercel
- **Names:** Vercel CLI
- **Old Tokens:** vercel-cli
- **Depends On:** Macos: >=: 13
- **Artifacts:** Binary: 2, Target: 2, Zap: 1
- **Deprecated:** no
- **Disabled:** no


## Related links

- [Homebrew Cask packages](https://pkg.so/homebrew-cask-packages/) - Generated from Homebrew Cask package-manager metadata.
- [Homebrew Cask binaries](https://pkg.so/homebrew-cask-binaries/) - Cask artifact metadata includes a binary.
- [netlify-cli](https://pkg.so/brew/netlify-cli/) - Choose Netlify CLI when the target hosting platform is Netlify and local development must reproduce Netlify redirects, edge logic, environment variables, and Functions.

  Sources: <https://vercel.com/docs/cli> · <https://docs.netlify.com/api-and-cli-guides/cli-guides/get-started-with-cli/> · <https://docs.netlify.com/api-and-cli-guides/cli-guides/local-development/>
- [cloudflare-wrangler](https://pkg.so/brew/cloudflare-wrangler/) - Choose Wrangler for Cloudflare Workers and Pages projects that need Cloudflare-specific local development, configuration, deployment, and resource management.

  Sources: <https://vercel.com/docs/cli> · <https://developers.cloudflare.com/workers/wrangler/> · <https://developers.cloudflare.com/workers/wrangler/commands/workers/>
- [vercel](https://pkg.so/brew/vercel/) - Same normalized package name exists in another local package ecosystem.

## Combined YAML source

View the package source record on GitHub. [combined/vercel.yml](https://github.com/mxcl/pkgdb/blob/main/combined/vercel.yml)


## Sources

- package-page enrichment
- curated configuration and credential file locations
- curated package history
- package version freshness
- package relationship graph
- cross-ecosystem install command graph
