jfrog / jfrog/jfrog-cli-security
Exclude test dependencies while running jf audit for a Maven project
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13
- Forks
- 50
- Avg merge
- 3d 48m
- Merged PRs (30d)
- 26
Description
If we run "jf audit --mvn" on a Maven project, it reports vulnerabilities from test dependencies. As per the current JFrog CLI documentation, there is a flag called "--exclude-test-deps" which applies to a Gradle project for excluding test dependencies. Hence, looking for the implementation of the same flag "--exclude-test-deps" for Maven projects as well.
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 --mvn entry point and compare its handling with the existing --exclude-test-deps behavior for Gradle. Trace how Maven dependencies are processed, then verify that enabling the flag excludes test dependencies while ordinary Maven audit behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, java
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100