-
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
[security] audit repository tooling #4459
Comments
Our current CodeQL is schedule to run at 1:30am every day, where the collector runs on pushes to main, and PRs. Should we update it? |
The recommendation is to run it on push to main and on PRs open-telemetry/sig-security#15 |
I think we can also use this issue to adopt the same tooling/automation in https://github.com/open-telemetry/opentelemetry-go-contrib |
Hello Team, I think we have already added codeQL. On the staticcheck front, please allow me to suggest golangcilint or staticcheck(https://staticcheck.io/docs/getting-started/), this is one of the most verbose & efficient staticcode checker as well a vulnerability analyser I have worked with. I can open a draftPR with it's integration if we are all on same page @pellared @MadVikingGod |
@sakshi-1505, we want to use |
Thanks @pellared for the update, I will open a PR for this. |
/assign |
Please check how other tools are versioned, installed and used via |
@pellared @codeboten We can close this issue now, we are all green! |
open-telemetry/opentelemetry-go-contrib#4413 is created. Closing this issue. |
The security SIG is looking to ensure that security tooling is setup consistently across the organization. As a result, we're asking maintainers to ensure the following tools are enabled in each repository:
Parent issue: open-telemetry/sig-security#12
The text was updated successfully, but these errors were encountered: