jfrog / jfrog/jfrog-cli-security
Jf docker scan results to add "Impact Pact" column
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13
- Forks
- 50
- Avg merge
- 3d 48m
- Merged PRs (30d)
- 26
Description
Description:
The current Jf docker scan results with an output where "impact Patch" is missing. However, the Xray reports downloaded from Xray and Artifactory UI are visible in the Impact path section. I'm attaching a sample outcome for reference.
Expected OutCome:
An additional column with the Impact path will help the developers point to the right descendant in a particular layer.
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 by locating the Docker scan result formatting and output entry points in this Go module, then compare their fields with the attached Xray or Artifactory example. Trace how impact-path data is represented in the scan response. Done means the Docker scan output includes an Impact path column that identifies the relevant descendant in each layer.
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