jfrog / jfrog/jfrog-cli-security

Show fix versions ranges in scan results

Open
#365 0 comments 0 reactions 0 assignees View on GitHub

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.
The fix versions of most of the vulnerabilities look like this: "[5.2.19]", but some of them look different, like this: "[1.1.1d-0+deb10u8, )". It's not clear that it represents a range of versions.

Describe the solution you'd like to see
Use the <, >, ≤, ≥ symbols to represent the ranges of the fix versions.
Read more here: https://docs.oracle.com/middleware/1212/core/MAVEN/maven_version.htm#MAVEN402
It needs to be changed in the 'table' and 'simple-json' formats of scan results.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the scan-result rendering for the table and simple-json formats, then inspect how fix-version values are currently formatted. Use the linked Maven version reference to confirm the range notation. Done means both formats display version ranges with comparison symbols, with tests covering the updated output.

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
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.