jfrog / jfrog/jfrog-cli-security
Request to have a Ondemand Scanning results URL in the output of On demand Scanning
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.
When we perform an on-demand scan on a docker image(Ex: jf docker scan), we get the vulnerability information in a table. However, the link to the Xray on-demand scan results is not available in the output. We had to manually open the JFrog Platform and navigate to the on-demand scan results under the Xray tab to view them. Hence, requesting a feature/improvement to have an on-demand Xray scan result URL on the JFrog CLI side.
$ jf docker scan larrycai/openldap
Describe the solution you'd like to see
The above result is available in Xray. Here we receive a table format response for the scan and additionally, we would expect the Xray on-demand scan result URL also to be printed as part of the output. Here is the sample URL which will help us to navigate directly. https://jpd.local/ui/onDemandScanning/3039e22b-87f2-47f8-473a-620170f4b072
Describe alternatives you've considered
The only alternative we have is, accessing the Xray application directly and get the Xray on-demand scan results.
Additional context
The above output of on-demand Xray scan in tabular fomat. This feature request is applicable to other formats as well such as Json, Sarif and Sample-json
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 jf docker scan entry point and inspect how its tabular, JSON, SARIF, and sample-JSON outputs are assembled. Determine how the on-demand Xray result URL is returned, then ensure the URL is included in each requested output format and verify the resulting output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100