jfrog / jfrog/jfrog-cli-security
Add option to include impact path in scan result table
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13
- Forks
- 50
- Avg merge
- 3d 48m
- Merged PRs (30d)
- 26
Description
Is your feature request related to a problem? Please describe.
It can be very difficult to find the source of a vulnerability from the table output of an xray scan. This makes it hard for developers to remediate the vulnerability.
Describe the solution you'd like to see
A flag (ie --include-impact-path) is added to the xray scan command that adds a column with the impact path.
Describe alternatives you've considered
The impact path is available in the json output, so that can be used, but it is much harder to read through. Developers can also go to the xray UI and find their scan, but depending on the volume of scans, it can be difficult to find the proper result.
Additional context
Add any other context or screenshots about the feature request here.
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 at the xray scan command and locate how its table output is built, then compare it with the JSON output where the impact path is already available. Trace how scan flags are parsed and verify that --include-impact-path adds the requested column while the default table output remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100