Skip to content
Back to search

vercel

Develop. Preview. Ship.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/vercel/vercel with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/vercel/vercel'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/vercel-vercel/badge.svg)](/listings/vercel-vercel)

HTML

<a href="/listings/vercel-vercel"><img src="/api/listings/vercel-vercel/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 220 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. <p align="center">
  2. <a href="https://vercel.com">
  3. <img src="https://assets.vercel.com/image/upload/v1588805858/repositories/vercel/logo.png" height="96">
  4. <h3 align="center">Vercel</h3>
  5. </a>
  6. </p>
  7. <p align="center">
  8. Develop. Preview. Ship.
  9. </p>
  10. <p align="center">
  11. <a href="https://vercel.com/docs"><strong>Documentation</strong></a> ·
  12. <a href="https://vercel.com/changelog"><strong>Changelog</strong></a> ·
  13. <a href="https://vercel.com/templates"><strong>Templates</strong></a> ·
  14. <a href="https://vercel.com/docs/cli"><strong>CLI</strong></a>
  15. </p>
  16. <br/>
  17. ## Vercel
  18. Vercel’s AI Cloud is a unified platform for building modern applications, giving teams the tools to be flexible, move fast, and stay secure while focusing on their products instead of infrastructure.
  19. ## Deploy
  20. Get started by [importing a project](https://vercel.com/new), [choosing a template](https://vercel.com/templates), or using the [Vercel CLI](https://vercel.com/docs/cli). Then, `git push` to deploy.
  21. ## Native CLI binaries
  22. The standard npm installation remains unchanged:
  23. ```bash
  24. npm i -g vercel
  25. ```
  26. Native CLI binaries are distributed separately and do not affect the `vercel` npm package. To opt into the native binary and replace existing global `vercel` and `vc` commands, install the native package explicitly:
  27. ```bash
  28. npm i -g @vercel/vc-native --force
  29. ```
  30. The `--force` flag allows npm to replace existing global `vercel` and `vc` bin links. Users who do not install `@vercel/vc-native` continue using the regular Node.js-based CLI from `npm i -g vercel`.
  31. Platform-specific packages are also available for direct installation when a specific binary is needed:
  32. ```bash
  33. npm i -g @vercel/vc-native-darwin-x64 --force
  34. ```
  35. ## Documentation
  36. For details on how to use Vercel, check out our [documentation](https://vercel.com/docs).
  37. ## Contributing
  38. This project uses [pnpm](https://pnpm.io/) to install dependencies and run scripts.
  39. You can use the `vercel` script to run local changes as if you were invoking Vercel CLI. For example, `vercel deploy --cwd=/path/to/project` could be run with local changes with `pnpm vercel deploy --cwd=/path/to/project`.
  40. When contributing to this repository, please first discuss the change you wish to make via [Vercel Community](https://community.vercel.com/tags/c/community/4/cli) with the owners of this repository before submitting a Pull Request.
  41. Please read our [Code of Conduct](./.github/CODE_OF_CONDUCT.md) and follow it in all your interactions with the project.
  42. ### Local development
  43. This project is configured in a monorepo, where one repository contains multiple npm packages. Dependencies are installed and managed with `pnpm`, not `npm` CLI.
  44. To get started, execute the following:
  45. ```bash
  46. git clone https://github.com/vercel/vercel
  47. cd vercel
  48. corepack enable
  49. pnpm install
  50. pnpm build
  51. pnpm lint
  52. pnpm test-unit
  53. ```
  54. Make sure all the tests pass before making changes.
  55. #### Running Vercel CLI Changes
  56. You can use `pnpm vercel` from the `cli` package to invoke Vercel CLI with local changes:
  57. ```bash
  58. cd ./packages/cli
  59. pnpm vercel <cli-commands...>
  60. ```
  61. See [CLI Local Development](./packages/cli#local-development) for more details.
  62. ### Verifying your change
  63. Once you are done with your changes (we even suggest doing it along the way), make sure all the tests still pass by running:
  64. ```bash
  65. pnpm test-unit
  66. ```
  67. from the root of the project.
  68. If any test fails, make sure to fix it along with your changes. See [Interpreting test errors](#Interpreting-test-errors) for more information about how the tests are executed, especially the integration tests.
  69. #### Reproducing affected builds and type-checks
  70. CI compares the pull request head with the base and head commits recorded by GitHub. To inspect the same affected Turborepo task plan locally, commit your changes, check out the pull request head, and set the explicit SCM range:
  71. ```bash
  72. export TURBO_SCM_BASE=$(gh pr view --json baseRefOid --jq .baseRefOid)
  73. export TURBO_SCM_HEAD=$(gh pr view --json headRefOid --jq .headRefOid)
  74. git fetch origin "$TURBO_SCM_BASE" "$TURBO_SCM_HEAD"
  75. test "$(git rev-parse HEAD)" = "$TURBO_SCM_HEAD"
  76. node utils/gen.js
  77. pnpm exec turbo run ci:checks --affected --dry=json
  78. ```
  79. To execute the selected tasks as CI does, replace the final command with:
  80. ```bash
  81. pnpm exec turbo run ci:checks --affected --output-logs=errors-only --summarize --continue
  82. ```
  83. Both commits must be available in the local clone; CI uses a full-history checkout and fails rather than treating a missing commit as an empty change. Lint, formatting, dependency checks, and generated asset validation remain repository-wide.
  84. ### Pull Request Process
  85. Once you are confident that your changes work properly, open a pull request on the main repository.
  86. The pull request will be reviewed by the maintainers and the tests will be checked by our continuous integration platform.
  87. ### Interpreting test errors
  88. There are two primary kinds of tests in this repository: unit tests and end-to-end (E2E) tests.
  89. Unit tests are primarily run with Vitest and execute quickly because they test isolated behavior.
  90. #### End-to-end tests
  91. Integration tests create deployments to your Vercel account using the `test` project name. After each test is deployed, the `probes` key is used to check if the response is the expected value. If the value doesn't match, you'll see a message explaining the difference. If the deployment failed to build, you'll see a more generic message like the following:
  92. ```log
  93. [Error: Fetched page https://test-8ashcdlew.vercel.app/root.js does not contain hello Root!. Instead it contains An error occurred with this application.
  94. NO_STATUS_CODE_FRO Response headers:
  95. cache-control=s-maxage=0
  96. connection=close
  97. content-type=text/plain; charset=utf-8
  98. date=Wed, 19 Jun 2019 18:01:37 GMT
  99. server=now
  100. strict-transport-security=max-age=63072000
  101. transfer-encoding=chunked
  102. x-now-id=iad1:hgtzj-1560967297876-44ae12559f95
  103. x-now-trace=iad1]
  104. ```
  105. In such cases, you can visit the URL of the failed deployment and append `/_logs` to see the build error. In the case above, that would be https://test-8ashcdlew.vercel.app/_logs
  106. The logs of this deployment will contain the actual error which may help you to understand what went wrong.
  107. ##### Running integration tests locally
  108. While running the full integration suite locally is not recommended, it's sometimes useful to isolate a failing test by running it on your machine. To do so, you'll need to ensure you have the appropriate credentials sourced in your shell:
  109. 1. Create an access token. Follow the instructions here https://vercel.com/docs/rest-api#creating-an-access-token. Ensure the token scope is for your personal
  110. account.
  111. 2. Grab the team ID from the Vercel dashboard at `https://vercel.com/<MY-TEAM>/~/settings`.
  112. 3. Source these into your shell rc file: `echo 'export VERCEL_TOKEN=<MY-TOKEN> VERCEL_TEAM_ID=<MY-TEAM-ID>' >> ~/.zshrc`
  113. From there, you should be able to trigger an integration test. Choose one
  114. that's already isolated to check that things work:
  115. ```bash
  116. cd packages/next
  117. ```
  118. Run the test:
  119. ```bash
  120. pnpm test test/fixtures/00-server-build/index.test.js
  121. ```
  122. > [!NOTE]
  123. > If you receive a `401` status code while fetching the deployment, you need to disable [Deployment Protection](https://vercel.com/docs/security/deployment-protection) on the project.
  124. #### @vercel/nft
  125. Some of the Builders use `@vercel/nft` to tree-shake files before deployment. If you suspect an error with this tree-shaking mechanism, you can create the following script in your project:
  126. ```js
  127. const { nodeFileTrace } = require('@vercel/nft');
  128. nodeFileTrace(['path/to/entrypoint.js'], {
  129. ts: true,
  130. mixedModules: true,
  131. })
  132. .then(o => console.log(o.fileList))
  133. .then(e => console.error(e));
  134. ```
  135. When you run this script, you'll see all the imported files. If files are missing, the bug is in [@vercel/nft](https://github.com/vercel/nft) and not the Builder.
  136. ### Deploy a Builder with existing project
  137. Sometimes you want to test changes to a Builder against an existing project, maybe with `vercel dev` or actual deployment. You can avoid publishing every Builder change to npm by uploading the Builder as a tarball.
  138. 1. Change directory to the desired Builder `cd ./packages/node`
  139. 2. Run `pnpm build` to compile typescript and other build steps
  140. 3. Run `npm pack` to create a tarball file. It is imporant to not use `pnpm pack` because it will not preserve the file permissions
  141. 4. Move the resulting tarball to a directory
  142. 5. Run `vercel <directory>` to upload the tarball file and get a URL. Remember to append `/<tarball name>` to then end of your URL
  143. 6. Edit any existing `vercel.json` project and replace `use` with the URL
  144. 7. Run `vercel` or `vercel dev` to deploy with the experimental Builder
  145. **Note:** You will need to turn off vercel authentication in settings -> deployment protection so the builder can be downloaded
  146. ## Reference
  147. - [Code of Conduct](./.github/CODE_OF_CONDUCT.md)
  148. - [Contributing Guidelines](./.github/CONTRIBUTING.md)
  149. - [Apache 2.0 License](./LICENSE)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.