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
{{ message }}
Repository navigation
Vulnerabilities And Secrets Do Not Raise Alerts #1120
I had a look at CodeQL earlier it is for a different thing and the reason it is passing is we have not added any checks to it.
And it mostly is used to avoid regression of security vulnerabilities in Application Code. The comment where I have explained this more here
For gitleaks, The reason it did not flag this was it thought the things that you are adding are false positives more details here
Activity
abbiemery commentedon Feb 25, 2026
@dan-fernandes Is this covered by the gitleaks lint?
dan-fernandes commentedon Mar 2, 2026
I've re-created the vulnerabilities PR and got this warning on push:
dan-fernandes commentedon Mar 2, 2026
The PR passes all CI, including CodeQL, so the issue is still open.
ZohebShaikh commentedon Mar 2, 2026
I had a look at CodeQL earlier it is for a different thing and the reason it is passing is we have not added any checks to it.
And it mostly is used to avoid regression of security vulnerabilities in Application Code. The comment where I have explained this more here
For gitleaks, The reason it did not flag this was it thought the things that you are adding are false positives more details here
I have seen gitleaks flag api-key etc