jfrog / jfrog/frogbot

The latest version of FrogBot is not detecting DotNet and NuGet

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

Nobody has claimed this yet.

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

Description

Describe the bug

While running FrogBot scan with the latest version on a .NET project, FrogBot is not determining the package manager. It shows the error message 'Couldn't determine a package manager or build tool used by this project. Skipping the SCA scan.' However, when I tested it with the older version 2.17.1, it detected the package manager successfully.

Current behavior

i runned two frogbot scan on my .net proejet with two differnet version but getting deiffernt result both times
when running frogbot with version 2.17.1 its scan the PR, but with version 2.19.6, it's not scanning

Case 1
Here how i am calling this step with version 2.17.1 and getting the log

- name: FrogBot
  if: ${{ env.JF_URL }}    
  uses: jfrog/frogbot@v2
  env:
    JF_URL: ***
    JF_ACCESS_TOKEN: ***
    JF_GIT_TOKEN: ***
    JF_WORKING_DIR: ***
    JF_FAIL: "FALSE"
  with:
    version: 2.17.1 

Log Screenshot : -

image

Case 2
Here how i am calling this step with version 2.19.6 and getting the log

- name: FrogBot
  if: ${{ env.JF_URL }}    
  uses: jfrog/frogbot@v2
  env:
    JF_URL: ***
    JF_ACCESS_TOKEN: ***
    JF_GIT_TOKEN: ***
    JF_WORKING_DIR: ***
    JF_FAIL: "FALSE"
  with:
    version: 2.19.6 

Log Screenshot : -

image

Reproduction steps

No response

Expected behavior

No response

JFrog Frogbot version

2.19.6

Package manager info

.NET CLI and NuGet

Git provider

GitHub

JFrog Frogbot configuration yaml file

No response

Operating system type and version

linux

JFrog Xray version

No response

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 running the GitHub Actions workflow shown in the issue against a .NET project with Frogbot versions 2.17.1 and 2.19.6, then compare the package-manager detection logs. Done means version 2.19.6 detects .NET CLI/NuGet and scans the pull request as the older version does.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, github-actions
Domain
ci-cd, security
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.