Skip to content

ci: add staticcheck and govulncheck to CI #96

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

Open
leno23 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

ci: add staticcheck and govulncheck to CI #96

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
6 changes: 6 additions & 0 deletions .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,3 +28,9 @@ jobs:

- name: go test
run: go test -race ./...

- uses: dominikh/staticcheck-action@v1
with:
version: latest

- uses: golang/govulncheck-action@v1
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot May 31, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Run govulncheck with the module's Go version

Because this step does not pass any inputs, golang/govulncheck-action@v1 uses its default go-version-input: stable and re-runs actions/setup-go; the govulncheck docs state that source scans use the go command on PATH as the build configuration. In this repo go.mod targets Go 1.20 and the build/release workflows use go-version-file: go.mod, so a standard-library vulnerability that affects Go 1.20 but is fixed in the latest stable Go would be missed by CI. Pass the same Go version/file into this action (or prevent it from overriding the existing setup) so the vulnerability scan matches the binary being built.

Useful? React with 👍 / 👎.