You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The `sinceleakperiod` parameter activates delta analysis. If `true`, sonar-report will only get the vulnerabilities that were added since a fixed date/version or for a number of days. For this it will:
@@ -64,10 +69,12 @@ More info:
64
69
- In sonarQube, /settings : see leak period
65
70
66
71
### allbugs
72
+
67
73
- "false": only vulnerabilities are exported
68
74
- "true": all bugs are exported
69
75
70
76
### fixMissingRule
77
+
71
78
On some versions of sonar (found on 6.5), the `type` of issue and the `type` of the rule don't match (for example `VULNERABILITY` vs `CODE_SMELL` ).
72
79
73
80
In this case, when `allbugs=false`, it's possible that the issue is extracted but not it's rule. What will happen is that the issue has `/` in the description (because the description is the name of the rule).
@@ -77,6 +84,7 @@ To circumvent this issue, the fixMissingRule will extract all rules without any
77
84
Beware that, with this parameter activated, all the issues linked to the rules displayed may not be displayed.
78
85
79
86
### noSecurityHotspot
87
+
80
88
Sonar-report will try to find how your sonarqube instance is working with hotspots depending on the running version. However in last resort, you can use the `--noSecurityHotspot="true"` flag in order to deactivate the hotspots processing.
81
89
82
90
**Note that you may miss out on some vulnerabilities when using this option if your sonarqube instance does support hotspots.**
@@ -121,7 +129,7 @@ Get the dependencies:
121
129
npm install
122
130
```
123
131
124
-
Run with the same command as [Use](#use) but use `node index.js` instead of `sonar-report`
132
+
Run with the same command as [Use](#use) but use `npm run build && npm run start` instead of `sonar-report`
0 commit comments