Merged
Conversation
Owner
martimlobao
commented
Jan 9, 2026
- remove from trunk
- remove from trunk
|
You have run out of free Bugbot PR reviews for this billing cycle. This will reset on February 25. To receive reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial. |
Contributor
Reviewer's guide (collapsed on small PRs)Reviewer's GuideAdds Checkov as a standalone IaC security check run via uv in CI and local Makefile workflows, removes its Trunk integration, and wires up minimal configuration to support running it through existing tooling. Flow diagram for updated make check with lint-checkovflowchart TD
MakeCheck["make check"]
MakeCheck --> LintCheckov["lint-checkov: uvx checkov -d ."]
MakeCheck --> LintJs["lint-jsort"]
MakeCheck --> LintOxipng["lint-oxipng"]
MakeCheck --> LintRuff["lint-ruff"]
MakeCheck --> LintRuffFormat["lint-ruff-format"]
MakeCheck --> LintRumdl["lint-rumdl"]
MakeCheck --> LintShellcheck["lint-shellcheck"]
MakeCheck --> LintShfmt["lint-shfmt"]
MakeCheck --> LintTombi["lint-tombi"]
MakeCheck --> LintTrufflehog["lint-trufflehog"]
MakeCheck --> LintTy["lint-ty"]
MakeCheck --> LintYamllint["lint-yamllint"]
LintCheckov --> CheckovCLI["Checkov via uvx (IaC security checks)"]
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
Contributor
There was a problem hiding this comment.
Hey - I've found 1 issue, and left some high level feedback:
- The
checkovinvocation is now duplicated between the Makefile and the GitHub Action; consider calling the Makefile target from the workflow (or vice versa) to keep behavior in one place and avoid future drift. - You previously pinned
checkovvia Trunk but now runuvx checkovwithout a version; if reproducibility matters, consider pinning the checkov version (e.g., via uv lockfile or explicit version) to avoid unexpected changes in CI behavior. - Enabling
ACTIONS_ALLOW_UNSECURE_COMMANDS: trueinvalidate_pr.yamlweakens GitHub’s security model; it would be good to document why this is needed or see if the semantic PR action can be configured in a way that doesn’t require this flag.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- The `checkov` invocation is now duplicated between the Makefile and the GitHub Action; consider calling the Makefile target from the workflow (or vice versa) to keep behavior in one place and avoid future drift.
- You previously pinned `checkov` via Trunk but now run `uvx checkov` without a version; if reproducibility matters, consider pinning the checkov version (e.g., via uv lockfile or explicit version) to avoid unexpected changes in CI behavior.
- Enabling `ACTIONS_ALLOW_UNSECURE_COMMANDS: true` in `validate_pr.yaml` weakens GitHub’s security model; it would be good to document why this is needed or see if the semantic PR action can be configured in a way that doesn’t require this flag.
## Individual Comments
### Comment 1
<location> `.github/workflows/validate_pr.yaml:22` </location>
<code_context>
- uses: amannn/action-semantic-pull-request@48f256284bd46cdaab1048c3721360e808335d50 # 6.1.1
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+ ACTIONS_ALLOW_UNSECURE_COMMANDS: true
</code_context>
<issue_to_address>
**🚨 issue (security):** Avoid enabling `ACTIONS_ALLOW_UNSECURE_COMMANDS` unless strictly necessary, as it weakens GitHub Actions security.
This re-enables deprecated, unsafe workflow commands and increases command injection risk. Please check whether a newer version or configuration of the semantic PR action can avoid this env var. If you must keep it, restrict its usage as much as possible and clearly document the rationale in the workflow file.
</issue_to_address>Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.