TheDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/DevDonzo/warden/llms.txt
Use this file to discover all available pages before exploring further.
status command gives you a quick, human-readable snapshot of Warden’s state in the current directory. It reads the last five scan result files from the scan-results/ folder, checks whether a .wardenrc.json configuration file is present, and reports whether the required environment tokens are set — all without running a scan or modifying any files.
status reads from the current working directory. Run it from your project root (the same directory where you run warden scan) to see accurate results.Synopsis
Flags
status takes no flags.
What it displays
Recent Scans
Warden looks for thescan-results/ directory in the current working directory. If it exists and contains .json files, the five most recent files are listed in reverse-chronological order (newest first). For each file, Warden reads:
- Filename — the scan result file name.
- Vulnerability count — taken from
summary.totalwhen present, or the length of thevulnerabilitiesarray as a fallback. - Date — derived from the
timestampfield inside the file, or from the filename itself if no timestamp is present.
No scan history found. If the directory does not exist at all, Warden prompts you to run warden scan first.
Configuration
Warden checks for a.wardenrc.json file in the current directory:
- Found →
✓ .wardenrc.json found - Not found →
⚠ No .wardenrc.json (using defaults)
Environment
Warden checks for two environment variables and reports their presence without revealing their values:| Variable | Set | Not set |
|---|---|---|
GITHUB_TOKEN | ✓ Set | ✗ Not set |
SNYK_TOKEN | ✓ Set | ✗ Not set |
Example output
Fully configured project with scan history
Fresh project, no scans yet
Project with scans but an unreadable result file
If a scan result file exists but cannot be parsed (for example, because it was truncated or corrupted), Warden printsUnable to parse next to that filename rather than failing:
Combining status with other commands
status is a read-only, zero-side-effect command. A typical workflow might look like:
warden status to quickly verify that environment tokens are present before handing off to CI, or to confirm that a previous scan produced output before running warden baseline --create.