Kusari Analysis Results:

✅ No Flagged Issues Detected
All values appear to be within acceptable risk parameters.

No pinned version dependency changes, code issues or exposed secrets detected!

@kusari-inspector rerun - Trigger a re-analysis of this PR
@kusari-inspector feedback [your message] - Send feedback to our AI and team
See Kusari's documentation for setup and configuration.
Commit: 960f52e, performed at: 2025-08-26T09:49:08Z

Found this helpful? Give it a 👍 or 👎 reaction!

Kusari PR Analysis rerun based on - d979586 performed at: 2025-08-26T09:52:24Z - link to updated analysis

As part of implementing this I have switched from the current hardcoded FORCE_COLOR=1 env variable to passing --color=always by default. As far as I understand this should have no functional difference, other than version support (with --color being supported from v1.5.0+ of Zizmor). I'm unsure if that incompatibility with old versions is worth working around.

Thanks for calling this out -- I think this'll be fine, since zizmor's official images don't even support versions before 1.5.2 🙂

Kusari PR Analysis rerun based on - 435d97b performed at: 2025-08-27T09:35:02Z - link to updated analysis

Kusari PR Analysis rerun based on - 960f52e performed at: 2025-08-27T10:06:06Z - link to updated analysis

Could you add it to the inputs section of the README as well?

Done, good catch 👍

I've also gone ahead and refactored the inputs so it's now color: false to disable the color, not color: never. The rest of the inputs look like they're designed as inputs to the action, not to zizmor, so color: false makes more sense ("never" only really makes sense if there's some kind of detection going on that we're disabling, as with zizmor, not if we're explicitly disabling color for the specific action invocation).