Scan your local projects for security vulnerabilities
135
Scan your source code and Docker images for security issues with the Vigilnz CLI.
Vigilnz detects:
Scan results are available in your Vigilnz dashboard.
Create an API key from your Vigilnz account.
You can provide the API key in two ways.
Linux / macOS:
export VIGILNZ_API_KEY="<apikey>"
Windows PowerShell:
$env:VIGILNZ_API_KEY="<apikey>"
Windows Command Prompt:
set VIGILNZ_API_KEY=<apikey>
Then use the variable in your Docker command.
Linux / macOS:
docker run --rm \
-e VIGILNZ_API_KEY \
-v "$PWD:/workspace:ro" \
vigilnz/cli:0.0.1 scan
Windows PowerShell:
docker run --rm `
-e VIGILNZ_API_KEY `
-v "${PWD}:/workspace:ro" `
vigilnz/cli:0.0.1 scan
Windows Command Prompt:
docker run --rm -e VIGILNZ_API_KEY -v "%cd%:/workspace:ro" vigilnz/cli:0.0.1 scan
You can also provide the API key directly in the Docker command.
Linux / macOS:
docker run --rm \
-e VIGILNZ_API_KEY="<apikey>" \
-v "$PWD:/workspace:ro" \
vigilnz/cli:0.0.1 scan
Windows PowerShell:
docker run --rm `
-e VIGILNZ_API_KEY="<apikey>" `
-v "${PWD}:/workspace:ro" `
vigilnz/cli:0.0.1 scan
Windows Command Prompt:
docker run --rm -e VIGILNZ_API_KEY="<apikey>" -v "%cd%:/workspace:ro" vigilnz/cli:0.0.1 scan
Your project is mounted as read-only, so Vigilnz does not modify your source code.
Scan a Docker image already available on your machine.
Linux / macOS:
docker run --rm \
-e VIGILNZ_API_KEY \
-v /var/run/docker.sock:/var/run/docker.sock \
--group-add 0 \
vigilnz/cli:0.0.1 scan-image <image>
Windows PowerShell:
docker run --rm `
-e VIGILNZ_API_KEY `
-v /var/run/docker.sock:/var/run/docker.sock `
--group-add 0 `
vigilnz/cli:0.0.1 scan-image <image>
Windows Command Prompt:
docker run --rm -e VIGILNZ_API_KEY -v /var/run/docker.sock:/var/run/docker.sock --group-add 0 vigilnz/cli:0.0.1 scan-image <image>
Example:
docker run --rm \
-e VIGILNZ_API_KEY \
-v /var/run/docker.sock:/var/run/docker.sock \
--group-add 0 \
vigilnz/cli:0.0.1 scan-image alpine:3.19
Docker image scanning requires access to the host Docker socket. The CLI does not use Docker-in-Docker and does not require
--privileged.
| Scan | Description |
|---|---|
| SAST | Detect insecure code patterns |
| Secret | Detect hardcoded secrets and credentials |
| SCA | Detect vulnerable dependencies |
| IaC | Detect infrastructure-as-code misconfigurations |
| SBOM | Generate a software bill of materials |
| Container | Scan Docker images for vulnerabilities |
docker run --rm \
-e VIGILNZ_API_KEY \
vigilnz/cli:0.0.1 whoami
docker run --rm vigilnz/cli:0.0.1 --help
docker run --rm \
-e VIGILNZ_API_KEY \
-v "$PWD:/workspace:ro" \
vigilnz/cli:0.0.1 scan --scan-types secret,sca
docker run --rm \
-e VIGILNZ_API_KEY \
-v "$PWD:/workspace:ro" \
vigilnz/cli:0.0.1 scan --json > report.json
Use Vigilnz CLI in your CI/CD pipelines to automatically detect security issues before deployment.
docker run --rm \
-e VIGILNZ_API_KEY \
-v "$PWD:/workspace:ro" \
vigilnz/cli:0.0.1 scan \
--fail-on high \
--remote
--fail-on high returns a non-zero exit code when high or critical findings are detected.
Current release: 0.0.1
For CI/CD pipelines, use a specific version such as vigilnz/cli:0.0.1 instead of latest to ensure consistent builds.
Currently supported:
Unlicensed
Content type
Image
Digest
sha256:2a6332640…
Size
56.8 MB
Last updated
about 1 month ago
docker pull vigilnz/cli:0.0.1