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 #126

Open
4 of 8 tasks
Tracked by #12
sakshi-1505 opened this issue Oct 22, 2023 · 2 comments
Open
4 of 8 tasks
Tracked by #12

[security] audit repository tooling #126

sakshi-1505 opened this issue Oct 22, 2023 · 2 comments

Comments

@sakshi-1505
Copy link

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

@sakshi-1505
Copy link
Author

@breedx-splk Can you please confirm if dependabot alerts are configured? Also, I don't see any java static checker configured for the repository, do you mind if I configure Sonarqube for our repository?

@breedx-splk
Copy link
Contributor

Hey @sakshi-1505 -- the java-based projects are now using (mend) Renovatebot for dependency scanning, not dependabot. The dashboard for renovate exists as an issue in our repo: #23

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants