jfrog / jfrog/jfrog-cli-security

JFrogAudit@1 Support For Exclusions Of Directories As Supported In CLI

Open
#506 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 JFrog Audit secrets scan in my Azure DevOps pipeline takes 14+ minutes to run. I believe this is partly because it is scanning a large directory of static assets that are provided by one of our vendors, which can be safely excluded from static code analysis.

Describe the solution you'd like to see
I would like the ability, in the JFrogAudit@V1 ADO task, to pass an argument to exclude certain directories. I see from the CLI documentation that this is supported in the CLI but the ADO task has no way to take advantage of it at this time. If I am missing something, please let me know.

Describe alternatives you've considered
I have tried to use the JFrogCLIV2@1 task but ran into various issues authenticating to the XRay server and gave up. Support for exclusions seems like a natural feature for this task.

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 comparing the JFrogAudit@V1 ADO task documentation with the linked CLI documentation for source-directory exclusions. Trace how the task accepts and forwards scan arguments, then check the repository's existing tests or task entry points. Done means users can specify directories to exclude in JFrogAudit@V1 and the exclusions affect the scan.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
devops, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 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.