liquidmetal-dev / liquidmetal-dev/battery
CI: add gosec security linter
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1
- Forks
- 0
- Avg merge
- 2h 13m
- Merged PRs (30d)
- 33
Description
.golangci.yml currently enables only the `standard` linter set plus errcheck/govet/staticcheck/unused/revive. There's no security-focused linter.
Add `gosec` to the golangci-lint config, and consider `bodyclose`/`contextcheck` too given the amount of gRPC/HTTP client code and context-passing in the reconciler and flintlock client packages.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with .golangci.yml and inspect the currently enabled linter set. Add gosec, then evaluate bodyclose and contextcheck against the gRPC/HTTP client code in the reconciler and flintlock client packages. Done means the CI linter configuration includes the intended security and context checks without introducing inappropriate findings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 78/100