Unpatched vulnerabilities are still printed with "suppressed"
- Dominant language
- JavaScript
- Stars
- 287
- Forks
- 95
- Avg merge
- 13h 23m
- Merged PRs (30d)
- 13
Description
I've noticed that unpatched vulnerabilities are still printed out with "suppressed".
I am running the action with the following config:
```
only-fixed: true
output-format: table
severity-cutoff: high
```
Yet, the output is as follows:
```
NAME INSTALLED FIXED-IN TYPE VULNERABILITY SEVERITY
apollo-server-core 3.10.2 3.11.0 npm GHSA-8r69-3cvp-wxc3 Medium
archiver 5.3.0 npm CVE-2006-1611 Medium (suppressed)
archiver 5.3.0 npm CVE-2018-25046 Critical (suppressed)
archiver 5.3.0 npm CVE-2019-10743 Medium (suppressed)
...
```
I expected
```
NAME INSTALLED FIXED-IN TYPE VULNERABILITY SEVERITY
apollo-server-core 3.10.2 3.11.0 npm GHSA-8r69-3cvp-wxc3 Medium
...
```
Contributor guide
Research direction
Reproduce the GitHub Action with only-fixed enabled, table output, and a high severity cutoff, then compare the rendered rows with the expected output in the issue. Trace how unpatched vulnerabilities are filtered and how the table labels suppressed findings; done means unpatched vulnerabilities are omitted rather than printed as suppressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100