Skip to content

ci: Tier 1 OSS security scanners (CodeQL + Dependabot + govulncheck + OSV-Scanner)#128

Merged
mastermanas805 merged 3 commits into
masterfrom
oss/tier1-security-scanners
May 21, 2026
Merged

ci: Tier 1 OSS security scanners (CodeQL + Dependabot + govulncheck + OSV-Scanner)#128
mastermanas805 merged 3 commits into
masterfrom
oss/tier1-security-scanners

Conversation

@mastermanas805
Copy link
Copy Markdown
Member

Summary

Adds GitHub-native + free OSS vulnerability scanners. All tools are 100% free for public repos — no API keys, no external accounts, no metered billing surface.

  • CodeQL (security-extended query suite) — SQL injection, XSS, SSRF, log injection, path traversal, race conditions
  • Dependabot — gomod + github-actions ecosystems, weekly schedule, grouped security PRs
  • govulncheck — Go-specific reachability-filtered CVE scan (eliminates false positives from unreachable code paths)
  • OSV-Scanner — cross-ecosystem CVE scan against Google's OSV.dev DB

Cost

Zero. All checks run on free GitHub Actions minutes for public repos.

Test plan

  • CodeQL workflow completes on PR (first run may take ~5 min)
  • govulncheck workflow passes (no reachable CVEs) or reports findings
  • OSV-Scanner workflow completes
  • Dependabot opens first batch of PRs on next Monday 06:00 UTC

🤖 Generated with Claude Code

Adds GitHub-native + free OSS vulnerability scanners. All tools are 100%
free for public repos — no API keys, no external accounts, no metered
billing surface.

- CodeQL with security-extended query suite (SQL injection, XSS, SSRF,
  log injection, path traversal, race conditions)
- Dependabot for gomod + github-actions (grouped security + version PRs)
- govulncheck (reachability-filtered CVE scan; Go-specific)
- OSV-Scanner (cross-ecosystem CVE scan against OSV.dev)

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@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.

mastermanas805 and others added 2 commits May 21, 2026 22:36
The Tier 1 CodeQL + govulncheck workflows failed on PR #128 because
this repo uses `replace instant.dev/common => ../common` and
`replace instant.dev/proto => ../proto` in go.mod. The scanners
checked out only api, so the sibling paths didn't resolve and the
`go build ./...` step exited 1.

Fix: each workflow now checks out api into ./api, plus clones
public sibling repos InstaNode-dev/common and InstaNode-dev/proto.
go build runs in api/, which can now resolve the replace targets.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
govulncheck on PR #128 flagged five Go-stdlib vulnerabilities reachable
from production code paths:

- GO-2026-4971 net.Dialer panic on NUL byte (Windows)
- GO-2026-4977 mail.ParseAddress edge cases
- GO-2026-4980 html/template unsafe contexts
- GO-2026-4982 html/template execute panic
- GO-2026-4986 mail.ParseAddress overflow

All fixed in Go 1.25.9–1.25.10. Bumping toolchain closes the
reachability paths flagged by govulncheck.

Also merges any in-flight master commits onto the scanner-install
branch so PR #128 reflects current master state.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@mastermanas805 mastermanas805 merged commit d8d0ab3 into master May 21, 2026
5 of 8 checks passed
@mastermanas805 mastermanas805 deleted the oss/tier1-security-scanners branch May 21, 2026 17:26
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