jfrog / jfrog/jfrog-cli-security
Is there a parameter in jf audit that can be used to prevent uploading the results to the UI page?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13
- Forks
- 50
- Avg merge
- 3d 48m
- Merged PRs (30d)
- 26
Description
Since the Xray On-Demand Scanning / Source code scans result page currently lacks permission control, anyone can view the scan results via the UI when using jf audit. Is there a parameter in jf audit that can be used to prevent uploading the results to the UI page?
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 audit command entry point and trace how Xray On-Demand Scanning and source-code scan results are uploaded to the UI. Determine whether an existing parameter can disable that upload; done means the behavior and any required option are confirmed, with the permission concern addressed or clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100