jfrog / jfrog/jfrog-cli-security
Control the depth of the gradle/maven/npm dependency tree (just like issue#202)
Open
Nobody has claimed this yet.
feature request
- 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.
no
Describe the solution you'd like to see
should support the option "max-tree-depth" for other package types.
the customer would like to use max-tree-depth for 'jf audit'
Describe alternatives you've considered
no
Additional context
no
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 existing max-tree-depth handling referenced by issue #202 and the jf audit command. Trace how dependency trees are built for Gradle, Maven, and npm, then verify that the option limits each tree to the requested depth.
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
- 35/100