[Automated] Update trivy CLI Options

[thomhurst]

Summary

This PR contains automatically generated updates to trivy CLI options classes.

The generator scraped the latest CLI help output from the installed tool.

Changes

• Updated options classes to reflect latest CLI documentation
• Added new commands if any were detected
• Updated option types and descriptions

Assembly-wide public API impact

No active public API changes were detected in this assembly.

Command coverage

Command coverage report:

• trivy (Version: 0.70.0): 31 commands, tree b9112521b915056fc75f902cabad65819a612532ebab47cf3d1cb8d0d264e789
  • Baseline comparison: 31 commands at Version: 0.70.0 -> 31 commands at Version: 0.70.0

Verification

• Solution builds successfully

---

🤖 Generated with ModularPipelines.OptionsGenerator

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)

• src/ModularPipelines.Trivy/Generated/Trivy.Generation.json is excluded by !**/generated/**

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: abab8b25-5adf-4dce-ae6f-ef3e7ea0647d

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Review: [Automated] Update trivy CLI Options (#4770)

This is an automated regeneration PR from ModularPipelines.OptionsGenerator. The diff touches a single file:

• src/ModularPipelines.Trivy/Generated/Trivy.Generation.json: only the generatorSourceSha256 field changes (from 773b4f9431... to bdf2981af6...). The toolVersion and commandTreeSha256 are unchanged, and no generated options/command classes were modified.

This is consistent with the generator's source having changed (e.g. a recent dependency bump touching tools/ModularPipelines.OptionsGenerator) without any change to trivy's actual CLI surface, so regeneration correctly produced identical output aside from the recorded source hash. No options classes were hand-edited, which matches the project's rule that generated output should only ever come from the scraper/generator.

No functional changes, no architectural concerns, nothing actionable here.

[github-actions]

Code Review — PR #4770

Scope: Single-file diff, 11 lines — src/ModularPipelines.Trivy/Generated/Trivy.Generation.json:

-  "generatorSourceSha256": "773b4f943140dab43ee649323893d06346286caa0635dcf177d0bfb536a63497"
+  "generatorSourceSha256": "4f583590c7bc1fb5c9bd0360c7986f13acb231fe933e1989457e137aa1339444"

No option classes, generator code, or other source files changed. toolVersion (0.70.0) and commandTreeSha256 are unchanged, matching the PR description (31 commands → 31 commands, same version) — trivy's actual CLI surface is unchanged.

I traced generatorSourceSha256 to scripts/GeneratedOptionsProvenance.ps1 (Get-GeneratedOptionsSourceFingerprint): it's a SHA-256 over the git blob/tree object IDs of a fixed list of generator-input paths (OptionsGenerator tool, shared CLI-option attribute/helper source, workflow file, Directory.Build.props, global.json, etc.) evaluated at HEAD. Since one of those inputs changed on main since trivy's provenance was last stamped, the fingerprint legitimately moved forward even though trivy's generated output is byte-identical. Assert-GeneratedOptionsFreshness.ps1 uses this field to detect staleness, so bumping it here is the correct, automated behavior of the "Generate CLI Options" workflow — not a hand-edit, consistent with the repo's rule that generated output is authoritative and shouldn't be hand-patched.

No actionable findings — this is a mechanical, correct provenance-hash update with no logic or behavior change.

[github-actions]

Code Review — PR #4770

Scope: Single-file diff — src/ModularPipelines.Trivy/Generated/Trivy.Generation.json, one field changed:

-  "generatorSourceSha256": "773b4f943140dab43ee649323893d06346286caa0635dcf177d0bfb536a63497"
+  "generatorSourceSha256": "bccbb8765ada5091f6455448d255ca004c6b2a462256b9df4a1c67688399d5f1"

toolVersion (0.70.0) and commandTreeSha256 are unchanged, matching the PR description (31 commands → 31 commands, same version). No trivy option/command classes were modified — trivy's actual CLI surface is unchanged, and nothing was hand-edited.

This is the same pattern already reviewed twice on this PR (see prior comments): the generatorSourceSha256 fingerprint is a hash over generator-input paths evaluated at HEAD, so it legitimately advances whenever any upstream generator input changes on main, even with byte-identical generated output for this tool. That's the correct, mechanical behavior of the regeneration workflow, consistent with this repo's rule that generated output is authoritative and must not be hand-patched.

No actionable findings — purely a provenance-hash bump with no logic or behavior change.