ci: SNYK checks for go dependencies
Open
Nobody has claimed this yet.
area/build
pinned
priority/P1
- Dominant language
- Go
- Stars
- 11.5k
- Forks
- 1.4k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 53
Description
We should run [snyk](https://snyk.io/) to check for vulnerabilities in our Go dependencies during CI.
Contributor guide
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 by reviewing the repository's CI configuration and Go dependency manifests. Add a Snyk vulnerability check for Go dependencies during CI, then verify that the workflow runs and reports dependency vulnerabilities as intended.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ci-cd, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100