[Automated] Update grype CLI Options

[thomhurst]

Summary

This PR contains automatically generated updates to grype 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:

• grype (grype 0.118.0): 12 commands, tree b45d7527254e3df6ad584cc8896f94ed1d24e359389729d279639a4563ceb40c
  • Baseline comparison: 12 commands at grype 0.118.0 -> 12 commands at grype 0.118.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.Grype/Generated/Grype.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: Team

Run ID: aca5cb4b-3e55-424f-9c9f-7d09030a53c1

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]

Code Review

This PR changes exactly one line in src/ModularPipelines.Grype/Generated/Grype.Generation.json, bumping generatorSourceSha256 from 773b4f9... to bdf2981a.... The toolVersion (grype 0.118.0) and commandTreeSha256 are unchanged, so no generated option classes actually changed — this is only the recorded hash of the generator's own source, indicating the generator was regenerated (likely because the generator tool changed elsewhere) but produced identical output for grype.

Per the project's conventions, this generated tracking file is exactly the kind of auto-generated artifact that shouldn't be hand-edited, and it isn't — it reflects a regeneration, which is the correct workflow.

There is no logic, conditional, or behavioral change in this diff, so there's nothing architectural or design-related to flag.

No actionable findings.

[github-actions]

Code Review

This PR changes exactly one line in src/ModularPipelines.Grype/Generated/Grype.Generation.json: generatorSourceSha256 moves from 773b4f9... to 4f583590.... toolVersion (grype 0.118.0) and commandTreeSha256 are unchanged, so no generated Grype option classes actually changed — this only records that the generator's own source was regenerated (e.g., a change elsewhere in tools/ModularPipelines.OptionsGenerator/) while producing identical output for this tool.

Per repo convention, this is a generated tracking artifact and per CLAUDE.md should never be hand-edited — it isn't; it's a clean regeneration output. There's no logic, conditional, or behavioral change in the diff, so there's nothing architectural or design-related to flag here.

No actionable findings.