Output of Markdown format does not seem to be showing all Packages/CVEs
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 454
- Forks
- 134
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I am noticing an issue when running the following command with the Docker Scout CLI wherein the markdown format does not seem to be outputting all packages/cve's being reported:
docker scout cves docker.arty-1.base.safe.com/fmeflow/fmeflow-core:devops-4448 --format markdown --output markdown.html
Attached Output:
If I run the default
docker scout cves docker.arty-1.base.safe.com/fmeflow/fmeflow-core:devops-4448 --output packages.txt
Attached Output:
Or alternatively an output of the Sarif format I do see all the CVE's:
docker scout cves docker.arty-1.base.safe.com/fmeflow/fmeflow-core:devops-4448 --format sarif --output test.sarif.json
Attached Output:
I am running these commands with
Docker Scout Version: v1.0.9 (go1.21.3 - windows/amd64)
Git Commit: 8bf95bf60d084af341f70e8263342f71b0a3cd16
On Windows 11 (23H2)
Thank you
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
Reproduce the reported docker scout cves command for the given image with the markdown, default, and SARIF formats, using the stated Docker Scout v1.0.9 environment as a reference. Compare the attached outputs to identify which packages or CVEs are omitted from markdown; done means markdown reports the same relevant findings as the other formats.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- cli, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100