Free · deterministic · no AI, no API key

Find it. Fix it.
Prove it.

VRA+ scans your code, dependencies, containers and infrastructure — then opens pull or merge requests with fixes that your own build and tests have already verified. What it can't fix safely, it hands to a human with the failure attached.

  • 1 binary
  • 3 scanners inside
  • 9 package ecosystems
  • 0 dependencies to install

~/my-app

$ vra scan --scanner all .
  trivy · semgrep · checkov  ──  63 findings
  CRITICAL 1  HIGH 25  MEDIUM 37
 
$ vra remediate --open-pr
  ✓ requests 2.25.1 → 2.33.0   build + tests pass
  ✓ lodash 4.17.15 → 4.18.0    npm build + test pass
  ✓ Dockerfile: run as non-root image builds
  ✓ pin actions/checkout to SHA
  ✗ PyJWT 1.7.1 → 2.14.0      tests fail → draft
 
  → PR    fix 40 security findings
  → draft needs manual fix — PyJWT
  → issue hardcoded secrets need rotation

One self-contained binary — the scanners ship inside it

  • Trivy dependencies · images · secrets
  • Semgrep source code (SAST)
  • Checkov IaC · Dockerfiles · CI configs

Why VRA+

You became a developer to build things.
Not to babysit CVEs.

Monday morning. The scanner has 63 new findings for you. Each one starts the same chore: read the advisory, find which version actually fixes it, check whether that version breaks anything, bump it, wait for the build, figure out why the tests went red, open a PR, chase a review.

By Thursday the list is shorter, the feature you planned hasn't moved, and the same two people on your team have done all of it — again.

Next Monday it's back. About 132 new CVEs are published every day1, against code you haven't touched in months. Security triage never finishes; it only waits for you.

72%

of developers spend more than 17 hours a week on security-related tasks — one in four spends more than 25.
Checkmarx, 2025 global developer study2

~25%

of security teams' time is spent remediating vulnerabilities — even when those vulnerabilities may be overrated or non-exploitable.
JFrog, Software Supply Chain State of the Union 20243

48,185

CVEs were published in 2025 — a record, and 20.6% more than the year before.
Jerry Gamblin, 2025 CVE Data Review1

82%

of practitioners say remediating a single vulnerability takes longer than 21 minutes — against an average backlog of 1.1 million.
Ponemon Institute & Rezilion, 20224

Without VRA+

  1. Read the scanner report and triage each finding
  2. Research advisories and fixed versions
  3. Pick a version that fixes every CVE without a breaking jump
  4. Edit manifests, overrides and lockfiles
  5. Build, test, debug, repeat
  6. Harden Dockerfiles and pin CI steps by hand
  7. Open PRs, write descriptions, chase reviews
  8. Do it all again next week

With VRA+

  1. vra scan and vra remediate --open-pr run in your pipeline
  2. You get a coffee
  3. You review one pull or merge request — every fix already built and tested
  4. Anything risky waits in a draft, with the failure output attached

What does it cost your team?

Set these to your own numbers. For reference, 82% of practitioners say one fix takes longer than 21 minutes4.

20 hours / month

≈ 2.5 working days, every month, on remediation — 240 hours a year.

Let VRA+ take care of it while you're getting your coffee.

Get your hours back
Sources
  1. Jerry Gamblin — 2025 CVE Data Review (48,185 CVEs in 2025 vs 39,962 in 2024; per-day figure is 48,185 ÷ 365).
  2. Checkmarx — Global study: developers still hampered by time spent on security, March 2025, 1,500 respondents.
  3. JFrog — Software Supply Chain State of the Union 2024, press release (PDF), March 2024, ~1,200 respondents.
  4. Ponemon Institute & Rezilion — The State of Vulnerability Management in DevSecOps, September 2022, 634 practitioners.

How it works

From finding to merged fix, without the guesswork

Scanners are good at telling you what's wrong. VRA+ does the next part: it changes the code, proves the change is safe, and delivers it for review.

  1. 01

    Scan

    Trivy, Semgrep and Checkov run together; findings are normalised, de-duplicated and grouped by type — SCA, SAST, IaC, secrets.

    vra scan
  2. 02

    Fix

    Each finding with a known, rule-based fix is applied in an isolated git worktree — one change at a time, most severe first.

    vra remediate --apply
  3. 03

    Prove

    Your build, your tests and a docker build of every Dockerfile must still pass, and a re-scan must show the finding gone.

    build · test · re-scan
  4. 04

    Deliver

    Verified fixes land in one pull or merge request. Anything that breaks the build becomes a draft with the change applied and the failure output.

    vra remediate --open-pr

What it fixes

Real fixes, not just a longer report

Every fix comes from a deterministic source — a scanner advisory, a rule's own fix, or a built-in hardening recipe. No model guessing at your code.

Vulnerable dependencies

Upgrades each package to the lowest version that closes every CVE, respecting backport release lines. Direct and transitive — via overrides, constraints and dependency management. Lockfiles are refreshed; formatting and line endings are kept. Major upgrades are flagged for review.

  • Maven
  • Gradle
  • npm
  • yarn
  • pnpm
  • pip
  • uv
  • Poetry
  • Go modules

Insecure code

Applies the fix that ships with the Semgrep rule — e.g. shell=True → shell=False. Refused if the file changed since the scan, and always marked for review.

Dockerfiles

Built-in hardening, each verified with a real image build:

  • run as a non-root user
  • pin base images to a digest
  • COPY instead of ADD
  • no SSH port 22
  • merge apt-get update with install
  • MAINTAINER → LABEL

CI supply chain

Pins third-party pipeline steps from a mutable tag to their full commit SHA — @v4 becomes @11d5960a… # v4 — so a moved tag can't change what your pipeline runs.

Hardcoded secrets

A committed secret must be revoked, not deleted. VRA+ opens one issue per repository with every location and the revoke → move → purge-history steps. Values are never copied.

Findings without a deterministic fix are listed too — nothing silently disappears.

Verification

A fix that breaks the build isn't a fix

Before touching anything, VRA+ runs every check on your untouched code. Then each fix has to pass all of them again.

  • Everything it touches is checked. A dependency bump must pass your tests and still build your Docker image — requests 2.33 passes on a modern Python but breaks a python:3.9 image. VRA+ catches that.
  • One change at a time. A failure is pinned to the change that caused it and never blocks the fixes that work.
  • No silent downgrades. A transitive pin that would undercut a related upgrade is skipped.
  • Your working tree is never touched. All work happens in a temporary git worktree; results land on branches.
  • Missing toolchain ≠ success. No mvn or docker on the machine? The fix is marked unverified and the PR says so.

Auto-detected build

pom.xmlmvnw verify
build.gradlegradlew build
package.jsoninstall · run build · run test
uv.lockuv sync · pip check · pytest
poetry.lockpoetry install · pip check · pytest
requirements.txtthrowaway venv · pip check · pytest
go.modgo build · go test
Dockerfile*docker build

Or bring your own: --verify-command "make ci"

What lands in your repo

Reviewable, idempotent, and honest about what failed

Re-running VRA+ updates everything in place — branches are force-pushed, PRs and issues edited, never duplicated.

PR / MR

vra/remediate

Every verified fix, grouped by kind, with what each one closes and the verification results.

VRA+: fix 40 security findings

✓ python ✓ web ✓ docker

Draft PR / MR

vra/needs-human/<name>

A fix that breaks the build — change already applied, failure output attached, and what was tried.

needs manual fix — PyJWT 1.7.1 → 2.14.0

E assert isinstance(token, bytes)

Issue

Secrets to rotate

A checklist of file:line and secret type, with revoke and history-purge steps.

VRA+: hardcoded secrets need rotation

☐ app/settings.py:5 — API token

GitHub pull requests and GitLab merge requests. Exit code 2 tells your pipeline some fixes need a human.

CI/CD

Just the CLI. No plugin, no app to install.

Download the binary in any pipeline and run two commands. A weekly schedule keeps your fix PR/MR current; merging it re-runs the scan.

  • GitHub Actions, GitLab CI, Jenkins — anything that runs a shell
  • Fail on CRITICAL, allow HIGH, or report-only with --no-fail
  • Configure with YAML, environment variables or flags

.github/workflows/vra.yml

on:
  schedule: [{ cron: "0 6 * * 1" }]
  push: { branches: [main] }

jobs:
  remediate:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
        with: { fetch-depth: 0 }
      - run: |
          curl -fsSLo vra https://github.com/gboie/vra-plus/releases/latest/download/vra-linux-amd64
          chmod +x vra && sudo mv vra /usr/local/bin/
      - run: vra scan --scanner all --no-fail .
      - run: vra remediate --open-pr || [ $? -eq 2 ]
        env:
          GITHUB_TOKEN: ${{ secrets.VRA_TOKEN }}

Pricing

Everything deterministic is free

If a fix doesn't need AI, it doesn't cost anything.

VRA+ Free

$0 forever

  • Scanning with Trivy, Semgrep and Checkov
  • Dependency upgrades in 9 ecosystems
  • Semgrep rule fixes
  • Dockerfile hardening
  • CI pipeline pinning to commit SHAs
  • Secrets rotation issues
  • Build-verified PRs/MRs, drafts for the rest
  • GitHub and GitLab; Linux, macOS and Windows
Install now

VRA+ AI coming soon

Paid add-on

  • AI-assisted fixes for findings with no rule-based fix
  • Help with the drafts that need a human
  • Same verification — your build still decides

Next on the roadmap: independent validation — a re-scan diffed against the original report to prove every CVE is closed.

Install

Up and running in a minute

No Python, no package manager, no scanners to install. The binary is named vra.

bash

curl -LO https://github.com/gboie/vra-plus/releases/latest/download/vra-linux-amd64
chmod +x vra-linux-amd64 && sudo mv vra-linux-amd64 /usr/local/bin/vra
vra --version
1vra scan --scanner all .

see what's wrong

2vra remediate

preview the plan — touches nothing

3vra remediate --apply

verified fixes on a local branch

4vra remediate --open-pr

push and open the PR