Skip to content

chore: dependency upgrades and Scorecard/security alert fixes - #33

Merged
KingPin merged 8 commits into
mainfrom
chore/deps-security-2026-11
Nov 11, 2026
Merged

KingPin merged 8 commits into
mainfrom
chore/deps-security-2026-11

Conversation

@KingPin

@KingPin KingPin commented Nov 11, 2026

Copy link
Copy Markdown
Owner

Summary

  • Upgrade all Go modules; go directive moves to 1.26 (required by prometheus/client_golang 1.25). Fixes GO-2026-6865, GO-2026-5841 (klauspost/compress, Dependabot alert Bump docker/build-push-action from 5 to 6 #1) and GO-2026-5024 (x/sys). govulncheck: no vulnerabilities.
  • Bump all actions to latest releases and pin by commit SHA (Scorecard PinnedDependencies).
  • CI builds with Go 1.27; gosec moves to ghcr.io/securego/gosec:2.30.0 (Docker Hub images stopped at 2.24.6).
  • Add G704/G706 rule IDs to existing #nosec annotations — gosec 2.30 renamed the SSRF check and added a log-injection check. Same justification as the existing G107 suppressions.
  • Pin Dockerfile builder to golang:1.27-alpine by digest.
  • Default workflow token to read-only; drop unused packages: write from the release job (Scorecard TokenPermissions).
  • Add SECURITY.md (private vulnerability reporting is now enabled) and a CodeQL workflow (Scorecard SecurityPolicy / SAST).

Supersedes #30, #31, #32.

Testing

  • go vet, go test -race ./... pass
  • gosec 2.30.0: 0 issues
  • actionlint: clean
  • docker build succeeds; image runs -version

Fixes GO-2026-6865, GO-2026-5841 (klauspost/compress) and
GO-2026-5024 (golang.org/x/sys). Supersedes #32.
Resolves Scorecard PinnedDependencies alerts. Supersedes #30 and #31.
gosec 2.30 reports SSRF as G704 (taint analysis) and log injection as
G706. Targets are operator-configured and validated at startup; the log
call uses %q.
gosec stopped publishing to Docker Hub after 2.24.6. The builder image
is pinned by digest (resolves Scorecard PinnedDependencies on Dockerfile).
Resolves Scorecard TokenPermissions alerts. The release job keeps
contents: write, which creating a GitHub release requires.
@KingPin
KingPin force-pushed the chore/deps-security-2026-11 branch from a75abd7 to 0831fb7 Compare November 11, 2026 15:03
@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@KingPin
KingPin merged commit 5140aaf into main Nov 11, 2026
3 checks passed
@KingPin
KingPin deleted the chore/deps-security-2026-11 branch November 11, 2026 15:52
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.

2 participants