CLI reference

argus fix

One step past scanning. fix plans a remediation for every advisory and writes the patched POMs to disk, still without modifying your project or talking to GitLab.

Synopsis

terminal
argus fix --pom pom.xml --out patches/

What it does

fix scans, then runs the strategy ladder to plan a remediation for each advisory and applies it with byte-level, format-preserving edits. The patched POMs are written to the directory given by --out (patches/ by default). Your real pom.xml is never modified, and nothing is published. fix is the way to see exactly what Argus proposes before any of it reaches a forge.

The output directory

Each patch is written as patches/<remediation-key>.pom.xml. The remediation key identifies the fix (the package and target version it addresses), so a project with several advisories produces one file per remediation. These files are complete POMs, not diffs: each is your original with the relevant edits spliced in.

Reviewing a patch

Because patches preserve formatting, diffing one against your original POM shows only the lines that changed, typically a version string and an annotation comment:

terminal
diff pom.xml patches/commons-text-1.10.0.pom.xml

See Output formats for the patch file naming, and Format-preserving patches for why the diff stays this small.