jfrog / jfrog/jfrog-cli-security
Security Issues in GitHub Step Summary is empty
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13
- Forks
- 50
- Avg merge
- 3d 48m
- Merged PRs (30d)
- 26
Description
Describe the bug
How to get to see the vulnerabilities in the GitHub Step Summary?
I tried everything... Nothing is working.
Documentation barely exists.
Generating Job Summary
/home/runner/_work/_tool/jf/2.88.0/x64/jf generate-summary-markdown
Warning: Failed populating code scanning sarif: HttpError: Unknown error: {"msg":"Invalid SARIF document: No valid runs found."}
What does this even mean?
I tried setting --format sarif for both jf docker scan and jf build-scan... Uploading the sarif files... Nothing works... The columns remain empty or show Not scanned...
Current behavior
nothing is displayed in the Security Issues column
Reproduction steps
In a GitHub workflow:
- build & push Docker image with docker/build-push-action
- jf docker scan
- jf rt build-docker-create
- jf rt build-collect-env
- jf rt build-add-git
- jf rt build-publish
- jf build-scan
Result: the Security Issues columns are completely empty.
Expected behavior
To see the vulnerabilities
JFrog CLI-Security version
?
JFrog CLI version (if applicable)
2.88.0
Operating system type and version
Ubuntu
JFrog Xray version
latest
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 listed GitHub workflow with JFrog CLI 2.88.0 on Ubuntu, including jf docker scan, jf rt build-* commands, and jf build-scan. Inspect the “Invalid SARIF document: No valid runs found” warning and compare the generated summary with the uploaded SARIF; done means vulnerabilities appear in the Security Issues column without empty or “Not scanned” results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, go
- Domain
- ci-cd, devops, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100