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

[security] audit repository tooling #418

Open
4 of 8 tasks
Tracked by #12
EjiroLaurelD opened this issue Oct 21, 2023 · 1 comment
Open
4 of 8 tasks
Tracked by #12

[security] audit repository tooling #418

EjiroLaurelD opened this issue Oct 21, 2023 · 1 comment
Labels
area:security Security and integrity issues

Comments

@EjiroLaurelD
Copy link

EjiroLaurelD commented Oct 21, 2023

Hello,
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:

  • CodeQL enabled via GitHub Actions
  • Static code analysis tool (the collector uses govulncheck [https://pkg.go.dev/golang.org/x/vuln] on every build)
  • Repository security settings
    • Security Policy ✅
    • Security advisories ✅
    • Private vulnerability reporting ✅
    • Dependabot alerts ✅
    • Code scanning alerts ✅

Parent issue: open-telemetry/sig-security#12

@atoulme
Copy link
Contributor

atoulme commented Nov 14, 2023

This repository doesn't use dependabot as dependencies are managed directly via the release process.
Static code analysis tool -> the repository uses shellcheck.

@mx-psi mx-psi added the area:security Security and integrity issues label Jan 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:security Security and integrity issues
Projects
None yet
Development

No branches or pull requests

3 participants