jfrog / jfrog/frogbot

fix vulnerability using dotnet command if nuget not exist

Open
#308 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request
Dominant language
Go
Stars
372
Forks
107
Avg merge
2d 20h
Merged PRs (30d)
5

Description

Is your feature request related to a problem? Please describe.
I'm using frogbot inside a docker that does not have nuget but uses dotnet commands.
when I run it I get:

Cloning repository with these details:
Clone url: [https://gitlab-ci-token:[MASKED]@gitlab.xxxx.net/develop/services/devops-xxxx.git](https://gitlab-ci-token:%5BMASKED%5D@gitlab.xxxx.net/develop/services/devops-xxxx.git) remote name: origin, branch: refs/heads/develop
 -----------------------------------------------------------------
Start fixing Microsoft.NETCore.App with 2.0.3
Creating branch: frogbot-Microsoft.NETCore.App-1da05d022e80e8fb1bff4c48ea5bf8fe
[Warn] failed while fixing Microsoft.NETCore.App with version: 2.0.3 with error: 
nuget  microsoft.netcore.app2.0.3 command failed: exec: "nuget": executable file not found in $PATH
[Info] Running git checkout to base branch: develop

Describe the solution you'd like to see
I would like it to use dotnet command instead of nuget

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 reproducing the reported vulnerability-fix flow in a Docker environment without nuget, using the logged Microsoft.NETCore.App 2.0.3 case. Trace where the failed nuget command is selected, then confirm the fix path can use a dotnet command and completes without the executable-not-found error.

Written by the indexing model from the issue text.

Assessment

Domain
security
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.