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

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

[security] audit repository tooling #1991

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

Comments

@sakshi-1505
Copy link

sakshi-1505 commented Oct 8, 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
Author

cc: @codeboten @lzchen

Please confirm if vulnerability reporting, dependabot alerts are configured for the repo as I don't have enough access to see those. I don't see us using any staticcode checker for Python, do you folks have any suggestion in mind for the same? I know we can use Mypy or Pylint.

@lzchen
Copy link
Contributor

lzchen commented Oct 9, 2023

This repo follows the same security rules as the core repo so we can use the issue in the original repo to discuss.

@lzchen lzchen closed this as completed Oct 9, 2023
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