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

Open
7 of 8 tasks
Tracked by #12
codeboten opened this issue Aug 21, 2023 · 2 comments
Open
7 of 8 tasks
Tracked by #12

[security] audit repository tooling #1073

codeboten opened this issue Aug 21, 2023 · 2 comments
Assignees

Comments

@codeboten
Copy link
Contributor

codeboten commented Aug 21, 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

@OluomaEsther
Copy link

Hello @codeboten I am Ogbodo Esther Oluomachukwu, an Outreachy applicant I want to contribute by ensuring security tooling is setup.

@austinlparker austinlparker self-assigned this Feb 19, 2024
@austinlparker
Copy link
Member

Given that the demo isn't a production application, and the wide number of languages, we'd like to opt-out of the static analysis. Let me know if this is a problem @open-telemetry/sig-security-maintainers

@puckpuck puckpuck removed the v1.9 label Nov 26, 2024
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

4 participants