Skip to content

Vekt

Vekt documentation

How to install the Vekt CLI, scan lockfiles, run it in CI, set up the language server in your editor, and use the browser extension.

Read the docs

Everything the CLI, the language server and the browser extension do.

  • Quickstart

    Install the Vekt CLI, run your first lockfile scan, read the output, and add it to CI.

  • CLI Reference

    Every Vekt CLI command, flag, exit code and environment variable, plus the .vektignore file format.

  • CI/CD Integration

    Gate builds on supply chain findings with vekt ci: GitHub Actions, GitLab CI, SARIF output and exit codes.

  • Supported Lockfiles

    Every lockfile format and ecosystem Vekt scans, with version notes and language server manifest support.

  • IDE Setup

    Set up vekt-lsp for supply chain diagnostics in VS Code, Neovim, Zed, Helix, Sublime Text, JetBrains and Emacs.

  • Browser Extension

    The Vekt browser extension adds a trust badge and typosquat warnings to package registry pages.

  • API Reference

    Vekt is local-first and has no cloud API. All scanning runs on your machine through the CLI.

  • FAQ

    Answers about Vekt: cost, offline use, private registries, false positives, finding types, trust scores and the browser extension.