Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sonarqube + dependency-check plugin for dotnet #473

Open
RunFox opened this issue Jul 27, 2021 · 4 comments
Open

Sonarqube + dependency-check plugin for dotnet #473

RunFox opened this issue Jul 27, 2021 · 4 comments
Labels
bug lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@RunFox
Copy link

RunFox commented Jul 27, 2021

Hello, I am use Sonarqube EE 8.4.2 with Dependency-Check plugin v 2.0.6
SonarQube parse json-report. But in logs for dotnet-project i see such info warning:
“INFO: No project configuration file, e.g. pom.xml, .gradle,.gradle.kts,package-lock.json found, therefore it isn’t possible to correctly link dependencies in file”.
And then:
“INFO: Linking 41 dependencies”
Can you tell me, please, what does it mean for dotnet-project and does it affect to work with vulnerable dependencies in sonar? As i see, sonar linking dependencies and create vulnerability in project page.

@RunFox RunFox added the bug label Jul 27, 2021
@Reamer
Copy link
Member

Reamer commented Aug 9, 2021

In general, we need to analyze the dotnet project file so that we can link new SonarQube issues against parts of this file.
I am not a dotnet developer, maybe you can help here.

@RunFox
Copy link
Author

RunFox commented Aug 9, 2021

Hello, @Reamer, thank you for answer. In project we have .csproj file and sonar links all issue with parts of code. I do not see any problem with work of SQ, only this warning.

@Reamer
Copy link
Member

Reamer commented Aug 11, 2021

This plugin converts all vulnerabilities found by dependency-check into SonarQube issues and tries to link these issues to a project file (e.g. pom.xml, package-lock.json ...). So this project file must be part of sonar.sources.

To find the correct line in this project file, the plugin analyzes this file.

If no project file is found as in your case this plugin links the issues against the SonarQube project. This has several disadvantages when working with the issues.

  • Solving problems within the UI does not work permanently

@github-actions
Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 19, 2022
@Reamer Reamer added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

2 participants