jfrog / jfrog/jfrog-cli-security
Publish the Vulnerability scan results to azure devops pipeline instead of hyperlink to jfrog artifactory
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13
- Forks
- 50
- Avg merge
- 3d 48m
- Merged PRs (30d)
- 26
Description
Publish the list of vulnerabilities in the pipeline runs tab , instead of hyperlink for build info
Description: Once the Build scan is completed in Azure devops pipeline using jfrog cli, publish build info task is publish the hyperlink to Buildinfo and display scan details in artifactory
Instead of link will it be possible to display the table with security threats,violations,license issues in build run itself
Example screenshot
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 Azure DevOps publish-build-info task and the JFrog CLI build scan integration in this Go module. Trace how scan results are currently represented and linked to Artifactory. Done means pipeline runs show vulnerability, security-threat, violation, and license-issue details directly instead of only a build-info hyperlink.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go
- Domain
- ci-cd, devops, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100