[Feature] Add number of vuln count per type to npm audit fix output
Open
Nobody has claimed this yet.
Enhancement
Release 7.x
- Dominant language
- JavaScript
- Stars
- 10.1k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 19
Description
Currently reify-output will also print the number of vulns per type, e.g:
found 611 vulnerabilities (608 low, 3 high)
run `npm audit fix` to fix them, or `npm audit` for details
It should also implement this style of count per type for npm audit fix output.
Current output:
fixed 606 of 611 vulnerabilities in 1618 scanned packages
5 vulnerabilities required manual review and could not be updated
Proposed output:
fixed 606 of 611 vulnerabilities in 1618 scanned packages
5 vulnerabilities (2 low, 3 high) required manual review and could not be updated
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 reify-output path that formats npm audit fix output. Compare its current manual-review message with the proposed per-severity format, then verify that the output reports the correct vulnerability counts by type.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100