Everything the CLI reads from and writes to a project's .vulnetix/ directory and the user's ~/.vulnetix/ directory, and which command owns each file.
Updated 02 Nov 2026Checked against cli@24498404a
Project: .vulnetix/
Created in the scanned directory (--path, or the current directory). Results are rewritten on each run. Add .vulnetix/ to .gitignore unless you commit the input files below on purpose; if you do, ignore the outputs and credentials.json explicitly.
Outputs
File
Written by
Contents
sbom.cdx.json
scan, sca, containers, license, cdx
CycloneDX SBOM with vulnerabilities and VEX analysis. Read by report.
sast.sarif
scan, sast, secrets, iac
SARIF for rule findings; only when there are findings
sca.sarif
every scan that runs SCA
SARIF for dependency findings. Written even when clean. See SARIF reference.
license.sarif
license
SARIF for licence findings. Written even when clean.
code-scanning/<kind>.sarif
gha publish code-scanning
The per-kind SARIF that was uploaded to GitHub
containers.sarif
containers, scan --only containers
SARIF for container file findings
malscan.sarif
malscan, the malscan pass of scan
SARIF for malware findings
cbom.cdx.json
cbom (and scan unless --no-cbom)
CycloneDX CBOM
ai-bom.cdx.json
aibom (and scan unless --no-aibom)
CycloneDX AIBOM
analyze.report.json
analyze
The analysis report
memory.yaml
scan and the scanners, ignore
Scan state, history and local suppression rules. Skipped with --disable-memory.