gosec: record why six rule classes stay excluded #633
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
#759 epic: code and supply-chain security hardening
sixfold-space/madtea
#623 gosec: handle every error
sixfold-space/madtea
Reference
sixfold-space/madtea#633
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
scripts/gosec.shexcludes six rule classes: G204, G301, G302, G304, G306, and G704. The reasons live only in the script header, with no decision record.With the error handling from #623 in place, gosec reports these hits in the six classes: G204 15, G301 8, G302 3, G304 46, G306 12, and G704 2.
Fix
docs/decisionsfor the six classes: for each class, every current site and why it is safe.scripts/gosec.shheader points at the record.Acceptance
scripts/gosec.shheader points at the record.adr checkpasses.