Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

conflicting security reports with other SCA tools

Open
#196 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
docker
Domain
security

Research direction

The issue provides no repository file, test, or entry point; it only identifies Docker Scout, Snyk Container, and their CVE databases. Start by locating where Docker Scout sources and compares vulnerability data, then compare its results with the Snyk database and define completion as consistent coverage of the relevant Snyk CVEs.

Written by the indexing model from the issue text.

Description

Docker Scout often presents more, or fewer CVE's compared with other SCA tools. For example, Docker Scout and Snyk Container tend to disagree on which CVE's apply to various images. Sometimes Docker Scout shows more CVE's. Sometimes Snyk Container shows more CVE's.

Can we please improve the CVE data for Docker Scout so that it behaves as a superset of the Snyk Database?

https://snyk.io/

https://security.snyk.io/

Dominant language
Shell
Stars
454
Forks
134
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from docker/scout-cli

All issues in docker/scout-cli

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.