jfrog / jfrog/jfrog-cli-security
"build-scan" should have different exit codes for different errors.
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13
- Forks
- 50
- Avg merge
- 3d 48m
- Merged PRs (30d)
- 26
Description
Scanning build with the CLI results with exit code 3 in several cases:
- When the build is not configured for scanning
- When there are vulnerabilities
There should be a different exit code for existing vulnerabilities and for build not scanned.
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 locating the build-scan CLI entry point and the existing exit-code handling. Trace the cases where the build is not configured for scanning and where vulnerabilities are found, then verify that each produces a distinct exit code; done means both behaviors are covered by tests or other repository validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100