Re-test one finding from a saved baseline and report whether it is resolved, still present, or unknown.
Stable in v3.7.0
Syntax
terminal
fendix verify <finding-id> --baseline <findings.json> (--url <url> | --code <path>) [flags]Arguments and required inputs
Provide exactly one finding ID, --baseline, and one of --url or --code.
Examples
Verify a finding
terminal
fendix verify SEC-001 --baseline results.json --url https://staging.example.comOptions
Scroll the table horizontally to inspect every column.
| Option | Type | Default | Requirement | Configuration | Environment | Description |
|---|---|---|---|---|---|---|
--auth | string | — | Optional | — | FENDIX_AUTH | Authorization header value (e.g. "Bearer ...") |
--baseline | string | — | Required | — | — | Path to the saved findings.json from the original scan (required) |
--code | string | — | Optional | — | — | Source code path (re-test file-anchored / dep findings; same as original --code) |
--enable-active | bool | false | Optional | scan.enable_active | — | Consent to re-send attack payloads when verifying an active-probe finding (mirrors the original scan's --enable-active) |
--json | bool | false | Optional | — | — | Emit JSON instead of the human-readable summary |
--timeout | int | 15 | Optional | scan.timeout | — | HTTP timeout in seconds (URL-anchored verify only) |
--url | string | — | Optional | — | — | Target URL (re-test URL-anchored findings; same as original --url) |