jfrog / jfrog/jfrog-cli-security
jf curation-audit / jd audit support for proxy in maven project
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13
- Forks
- 50
- Avg merge
- 3d 48m
- Merged PRs (30d)
- 26
Description
Support for proxy in jfog-cli audit and curation-audit
jf support proxy according to https://jfrog.com/help/r/jfrog-applications-and-cli-documentation/proxy-support
This indeed work for the frog-cli itself, how ever when interacting with maven project, jf tries to generate a settings.xml but does not include proxy configuration.
Generating a settings.xml with proxy configuration
The jfrog-cli should check if HTTPS_PROXY / HTTP_PROXY exist or not, and should try to find the host and its port and generate the xml file according to this https://maven.apache.org/guides/mini/guide-proxies.html.
the issue is from the function: https://github.com/jfrog/jfrog-cli-security/blob/main/sca/bom/buildinfo/technologies/java/mvn.go#L231
Alternative way
Another way is to provide the settings.xml with the command line so we can override the configuration
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 in sca/bom/buildinfo/technologies/java/mvn.go at the referenced line, then review JFrog CLI proxy support and Maven's proxy configuration guide. Trace how settings.xml is generated and determine whether HTTPS_PROXY/HTTP_PROXY or a command-line settings.xml override is supported. Done means Maven audit and curation runs honor the selected proxy configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, java
- Domain
- build-system, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100