-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Add Semgrep as static analyser for CI #3961
Comments
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
|
This is still in progress ( and I hope that it will be finished soon) |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
|
We are blocked by semgrep/semgrep#7121 |
Proposal
We are already using go linters and also CodeQL for detecting code smells and potential code vulnerabilities. Semgrep is another interesting tool that can help us with this job as it has some interesting rules that we can extend.
Use-Case
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: