---
title: "@vercel/cli-exec 1.0.1: release notes, upgrades and advisories"
description: "@vercel/cli-exec 1.0.1: release notes, breaking changes by major version and no known security advisory."
url: https://inlinr.com/packages/@vercel/cli-exec
lang: en
---

[Packages](https://inlinr.com/packages)

# @vercel/cli-exec

1.0.1 · 3 Aug 2026 Apache-2.0 18.1M / week [Repository](https://github.com/vercel/vercel) [Homepage](https://vercel.com/) [npm](https://www.npmjs.com/package/@vercel/cli-exec) [Atom feed](https://inlinr.com/packages/feed/@vercel/cli-exec)

Your version 

## Where each line stands

[Plan an upgrade](https://inlinr.com/packages/@vercel/cli-exec/upgrade)

LineNewestSecurity

- 1.x 1.0.1 No known advisory Latest line
- 0.x 0.1.1 No known advisory [To 1.0.1](https://inlinr.com/packages/@vercel/cli-exec/upgrade/0.1.1-1.0.1)

## Latest releases

1. 1.x · latest line
2. ### [1.0.1](https://inlinr.com/packages/@vercel/cli-exec/releases/1.0.1 "Open this release") [](https://github.com/vercel/vercel/blob/HEAD/packages/cli-exec/CHANGELOG.md "Read this release where it was published")  
3 Aug 2026

  - Bump all workspace packages to trigger a full publish from vercel-internal.
3. ### [1.0.0](https://inlinr.com/packages/@vercel/cli-exec/releases/1.0.0 "Open this release") [](https://github.com/vercel/vercel/releases/tag/%40vercel/cli-exec%401.0.0 "Read this release where it was published")  
18 Jun 2026

  - Breaking  
  Improve project-local `vercel` binary lookup fidelity by resolving only through the local `vercel` package, stopping lookup at project boundaries, and skipping directories that have unsafe ownership or access mode. Major bump, because `findVercelCli` has been made async and `clearVercelCliCache` renamed to `clearVercelCliLookupCache`. It is also substantially a complete rewrite.
4. 0.1.x · maintenance
5. ### [0.1.1](https://inlinr.com/packages/@vercel/cli-exec/releases/0.1.1 "Open this release") [](https://github.com/vercel/vercel/releases/tag/%40vercel/cli-exec%400.1.1 "Read this release where it was published")  
9 May 2026

  - Bump only

Dependency tracking

## Know when your own dependencies move

@vercel/cli-exec shipped a new major in the last 12 months, among 4 releases. inlinr shows which of your projects are behind, and what the upgrade breaks.

- Advisories reach you  
An email when a critical or high advisory affects a project, before the next install.
- Upgrades checked first  
Peer ranges, Node, ESM-only and types changes read before you bump.
- Only what matters  
Majors and breaking notes stay; patches and sibling bumps fold into one line.

[How dependency tracking works](https://inlinr.com/dependencies)

## Security

No known security advisory.

## Health of 1.0.1

[Details](https://inlinr.com/packages/@vercel/cli-exec/security#signals)

- **Provenance**: None
- **Publisher**: GitHub Actions
- **Maintainers**: 4
- **Scorecard**: 6.1 / 10
- **Size**: 134 kB

## Weekly downloads

## Same family

- [@vercel/oidc 71.4M/wk](https://inlinr.com/packages/@vercel/oidc)
- [@vercel/cli-config 26.7M/wk](https://inlinr.com/packages/@vercel/cli-config)
- [@vercel/functions 16.1M/wk](https://inlinr.com/packages/@vercel/functions)
- [@vercel/nft 15.5M/wk](https://inlinr.com/packages/@vercel/nft)
- [@vercel/analytics 10.8M/wk](https://inlinr.com/packages/@vercel/analytics)
- [@vercel/build-utils 7.9M/wk](https://inlinr.com/packages/@vercel/build-utils)
- [@vercel/sandbox 7.7M/wk](https://inlinr.com/packages/@vercel/sandbox)
- [@vercel/error-utils 7.5M/wk](https://inlinr.com/packages/@vercel/error-utils)

Reading releases, release notes and advisories…

Registry facts last checked 20 Nov 2026\. Releases and advisories last read 20 Nov 2026.

A whole project to check? Paste its package.json in the [dependency check](https://inlinr.com/tools/dependency-check): every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.
