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

Closed
8 tasks done
Tracked by #12
sakshi-1505 opened this issue Oct 10, 2023 · 2 comments · Fixed by #4417
Closed
8 tasks done
Tracked by #12

[security] audit repository tooling #4413

sakshi-1505 opened this issue Oct 10, 2023 · 2 comments · Fixed by #4417
Assignees

Comments

@sakshi-1505
Copy link
Contributor

sakshi-1505 commented Oct 10, 2023

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
Contributor Author

@pellared Please confirm if we have dependant alerts enabled as well as vulnerability reporting for the repo.

@sakshi-1505
Copy link
Contributor Author

/assign

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

Successfully merging a pull request may close this issue.

1 participant