Unable to filter out CVEs with added exceptions and missing documentation for --ignore-suppressed usage
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 141
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Description
Hi Docker Scout team,
First of all, thank you for all your hard work on Docker Scout!
I am trying to filter out CVEs that have already been suppressed/ignored In the Docker Scout Web App for our organisation. In the v1.13.0 release notes, it states:
Add --ignore-suppressed filter option to cves and quickview commands to filter out CVEs affected by Scout suppressions.
However, I have not been able to find any documentation or examples showing how to use the --ignore-suppressed option, particularly within the GitHub Action context.
Could you please provide guidance or documentation on:
- How to set up the
--ignore-suppressedoption within my GitHub Action/workflow? - Any required steps or configurations to ensure that suppressed CVEs are correctly filtered out?
Thank you in advance for your help and clarification!
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 with the v1.13.0 release notes and the Docker Scout GitHub Action workflow usage, then trace how the --ignore-suppressed option is passed to cves or quickview. Done means the action's documentation includes a working workflow example and any required configuration for filtering suppressed CVEs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions
- Domain
- ci-cd, documentation, security
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100