GitHub Action
The Setup Vulnlog CLI action installs the Vulnlog CLI on a GitHub Actions runner and puts vulnlog on the PATH.
After the action, every step of the job can call vulnlog.
The action is vulnlog/setup-vulnlog.
It’s on the GitHub Marketplace, and its source is in the vulnlog/setup-vulnlog repository.
For a complete workflow, see Run in CI pipelines.
Usage
steps:
- uses: actions/checkout@v7
- uses: vulnlog/setup-vulnlog@v1
with:
version: 0.19.0
- run: vulnlog validate --strict acme-shop.vl.yaml
The action needs no token and no permissions block.
It downloads public release assets from GitHub only.
Inputs
| Input | Default | Description |
|---|---|---|
|
|
Version to install, for example |
With latest, a job picks up each new release as soon as it’s published.
With a fixed version, every run uses the same Vulnlog version.
Outputs
| Output | Description |
|---|---|
|
The installed version, without the leading |
|
|
|
Absolute path of the |
|
|
Runners
The action installs the native binary where one exists, and the JVM distribution on the other runners.
| Runner | Distribution | Needs Java |
|---|---|---|
|
|
no |
|
|
no |
|
|
no |
|
|
yes |
|
|
yes |
The JVM distribution needs Java 21 or later, installed before the action. Without Java 21 or later, the step fails. These steps install Java first:
- uses: actions/setup-java@v6
with:
distribution: temurin
java-version: '21'
- uses: vulnlog/setup-vulnlog@v1
Vulnlog releases don’t publish checksums or build attestations, so the action doesn’t verify the download.