New check: check for dependency scanner
Open
Nobody has claimed this yet.
kind/enhancement
- Dominant language
- Go
- Stars
- 5.7k
- Forks
- 724
- Avg merge
- 19h 30m
- Merged PRs (30d)
- 1
Description
Dependency (vuln) canners may be for package managers (cargo-audit, npm-audit, etc), for docker (snyk), github apps (dependabot), etc
We could add a test to see if a scanner is used as part of a github workflow. This check may live under the existing SATS check?
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 reading the existing SATS check and how checks inspect GitHub workflows. Compare the mentioned package-manager, Docker, and GitHub-app scanners, then define the supported workflow evidence. Done means the check reliably identifies whether a dependency vulnerability scanner is used in a workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions
- Domain
- ci-cd, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100