Skip to content
VS Code

lockvet for VS Code

io.github.matteo-sung/lockvet

Explain any lockfile or workflow-pin change: bumps, vulns, ages, deprecations — 61 formats

client:VS Code transport:stdio runtime:oci

Install lockvet in VS Code

.vscode/mcp.json

{
  "inputs": [
    {
      "type": "promptString",
      "id": "github-token",
      "description": "GITHUB_TOKEN",
      "password": true
    },
    {
      "type": "promptString",
      "id": "gitlab-token",
      "description": "GITLAB_TOKEN",
      "password": true
    },
    {
      "type": "promptString",
      "id": "bitbucket-token",
      "description": "BITBUCKET_TOKEN",
      "password": true
    },
    {
      "type": "promptString",
      "id": "gitea-token",
      "description": "GITEA_TOKEN",
      "password": true
    },
    {
      "type": "promptString",
      "id": "azure-devops-token",
      "description": "AZURE_DEVOPS_TOKEN",
      "password": true
    }
  ],
  "servers": {
    "lockvet": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/matteo-sung/lockvet:0.6.20"
      ],
      "env": {
        "GITHUB_TOKEN": "${input:github-token}",
        "GITLAB_TOKEN": "${input:gitlab-token}",
        "BITBUCKET_TOKEN": "${input:bitbucket-token}",
        "GITEA_TOKEN": "${input:gitea-token}",
        "AZURE_DEVOPS_TOKEN": "${input:azure-devops-token}"
      }
    }
  }
}

VS Code prompts for each input the first time the server starts, so no secret is written to the file. VS Code docs

lockvet in other clients