Just the CVE's, M'am

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
docker, shell
Domain
cli, security

Research direction

Start by tracing Docker Scout CLI's report-generation entry point and compare its output with the linked GitHub Actions run. Determine where report verbosity or formatting is selected, then verify that a minimal CVE-only report can be selected and that the default output matches the requested behavior.

Written by the indexing model from the issue text.

Description

Like many security tools, Docker Scout's report format is too verbose. This triggers GitHub Actions CI/CD text length limits. Which then triggers a low level Actions false positive glitch. Which prevents security notifications from sending.

https://github.com/mcandre/octane/actions/runs/13930440668/job/38985990400

Could there be an option to present a more minimalistic report with just the CVE ID's line by line? Preferably the default behavior.

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.