Skip to content

fix(security): address code-security scan findings - #14

Merged
odsod merged 3 commits into
mainfrom
fix/security-scan-findings
Aug 3, 2026
Merged

fix(security): address code-security scan findings#14
odsod merged 3 commits into
mainfrom
fix/security-scan-findings

Conversation

@odsod

@odsod odsod commented Aug 3, 2026

Copy link
Copy Markdown
Member

Summary

  • Pin GitHub Actions to commit SHAs (mutable tags enable supply-chain attacks)
  • Add cooldown period to dependabot config
  • Use crypto/rand instead of math/rand/v2 for retry jitter

Test plan

  • mise run lint and mise run test pass locally

odsod added 3 commits August 3, 2026 12:58
Tags and branch names can be silently repointed by the action owner,
enabling supply-chain attacks (as seen in the trivy-action and
kics-github-action compromises). Pin every action reference to its
resolved commit SHA, keeping the version tag as a trailing comment.
Newly published package versions can be malicious or unstable.
Wait 7 days before Dependabot resolves new gomod and github-actions
releases, giving time for supply-chain issues to surface.
math/rand/v2 is not cryptographically secure. Retry jitter doesn't
need CSPRNG-strength randomness, but crypto/rand avoids flagging the
code path as a predictable-randomness finding in security scans.
@odsod
odsod force-pushed the fix/security-scan-findings branch from 8a288a6 to 0f32383 Compare August 3, 2026 11:10
@odsod
odsod merged commit 803ac32 into main Aug 3, 2026
1 check passed
@odsod
odsod deleted the fix/security-scan-findings branch August 3, 2026 11:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants