Skip to content

ci: document how the embedded gosec policy differs from the standalone gate #2246

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
cristim merged 1 commit into from
Oct 16, 2026
Merged

ci: document how the embedded gosec policy differs from the standalone gate #2246

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions .golangci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,13 @@ linters:
sizeThreshold: 1024
gocyclo:
min-complexity: 10
# gosec here is a code-hygiene signal, narrower than the enforcing gate
# scripts/run-gosec.sh (CI, pre-commit, Make; all rules, all severities,
# no config file, #nosec honored). Here G104 is excluded, severity and
# confidence are medium+, and the legacy/common-false-positives presets
# drop G301/G302/G304; gosec is also skipped in _test.go (the standalone
# scan omits tests by default). A clean golangci run does not imply a
# clean gosec run.
gosec:
excludes:
- G104
Expand Down
Loading