jfrog / jfrog/jfrog-cli-security
In JF CLI v 2.71.3, scanning with --repo-path does not generate violations
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13
- Forks
- 50
- Avg merge
- 3d 48m
- Merged PRs (30d)
- 26
Description
Describe the bug
In JF CLI v 2.71.3, scanning (jf s \ jf docker scan) with --repo-path is not generating violations.
Current behavior
Scanning (jf s \ jf docker scan) with --repo-path is not generating violations.
--watches flag is working as expected and generating violations.
Reproduction steps
Scan a binary using jf s \ scan a docker image using jf docker scan, with the --repo-path flag.
Expected behavior
Getting violations according to the watches that are configured for the mentioned repository.
JFrog CLI-Security version
2.71.3
JFrog CLI version (if applicable)
2.71.3
Operating system type and version
NA
JFrog Xray version
3.106.7
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 by reproducing the issue with jf s and jf docker scan using --repo-path, then compare the behavior with the working --watches flag. Done means scans for binaries and Docker images generate violations according to watches configured for the repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100