jfrog / jfrog/jfrog-cli-security
jf audit Test dependencies exclusions coherence
Open
Nobody has claimed this yet.
question
- Dominant language
- Go
- Stars
- 13
- Forks
- 50
- Avg merge
- 3d 48m
- Merged PRs (30d)
- 26
Description
Hi,
In jf audit documentation, I can read that --exclude-test-deps allows to exclude Gradle test dependencies from Xray Scanning.
I am wondering why this is not possible for maven dependency scan ?
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 with the jf audit documentation and the --exclude-test-deps option described for Gradle test dependencies. Compare that behavior with the Maven dependency scan and determine what equivalent exclusion is expected for Xray scanning; done means the requested Maven behavior is clearly defined and supported or 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
- Mostly clear
- Newbie friendliness
- 30/100