Skip to content

Run gosec through its GitHub Action - #112

Merged
korya merged 1 commit into
masterfrom
korya-chore-use-gosec-action
Aug 31, 2026
Merged

Run gosec through its GitHub Action#112
korya merged 1 commit into
masterfrom
korya-chore-use-gosec-action

Conversation

@korya

@korya korya commented Aug 31, 2026

Copy link
Copy Markdown
Owner

Problem

CI compiles gosec from source on every run even though gosec provides a maintained GitHub Action.

This adds avoidable setup work and bypasses the integration maintained by the scanner project.

Solution

Run gosec through its official GitHub Action and keep the remaining static checks in the existing job.

Check group Before After
gosec Compile with go install, then invoke through just Invoke through securego/gosec@master
Other static checks Invoke through just static-checks Invoke the same non-security recipes through just

The action's master ref is the upstream-documented stable channel and currently selects gosec 2.29.0 through a digest-pinned container image. Local development continues to use the existing just security and just pre-commit commands.

Other Changes

None. No visual change.

🤖 Generated with Claude Code

Use gosec's maintained action instead of compiling the scanner during every CI run. Keep the
remaining repository checks in the existing job after the dedicated security scan.

Co-Authored-By: OpenAI Codex (GPT-5) <noreply@openai.com>
@korya
korya marked this pull request as ready for review August 31, 2026 02:28
@korya
korya merged commit ae6a742 into master Aug 31, 2026
8 checks passed
@korya
korya deleted the korya-chore-use-gosec-action branch August 31, 2026 02:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant