jfrog / jfrog/jfrog-cli-security

Ignore pip and setuptools vulnerabilities on 'jf audit'

Open
#388 0 comments 3 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.

When Running 'jf audit' command on an empty python project, there are still vulnerabilities on pip and setuptools, even though the project is empty and does not contain any reference to pip or setuptools.

Describe the solution you'd like to see

'audit' should report vulnerabilities based on what is present on the venv after pulling the dependencies and should ignore pip and setuptools as long as they are not part of the project requirement file.

Describe alternatives you've considered

Another way is to add an option to ignore specific CVE's as vulnerabilities on the scan.

Additional context

TBD

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

The issue names no files or tests; start by tracing the jf audit command's Python virtual-environment dependency collection and how it compares packages with the project requirement file. Reproduce the empty-project case, then verify that pip and setuptools are excluded unless referenced by the requirements and that unrelated vulnerability reporting remains unchanged.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.