-
Notifications
You must be signed in to change notification settings - Fork 10
Issues: open-telemetry/sig-security
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Guidance/Requirements for assets managed and controlled by OpenTelemetry
#80
opened Nov 25, 2024 by
svrnm
Define communications strategy (blog posts, social media posts...) after a CVE is released
#63
opened Aug 13, 2024 by
mx-psi
Enable OpenSSF Scorecard to enhance security practices across the project
#57
opened Jul 19, 2024 by
harshitasao
What should we do with the sigstore files?
code signing
Items related to questions, best practices and recommendations around code signing
#53
opened Jul 8, 2024 by
ocelotl
Looking for advice on signing artifacts for Weaver / semantic conventions
code signing
Items related to questions, best practices and recommendations around code signing
#47
opened Jun 5, 2024 by
jsuereth
Enabling SBOM across repositories
sbom
Items related to questions, best practices, and recommendations for SBOMs
#33
opened Nov 15, 2023 by
codeboten
Where to publish Java signing pubkey?
code signing
Items related to questions, best practices and recommendations around code signing
#14
opened Aug 30, 2023 by
breedx-splk
Investigate code signing
code signing
Items related to questions, best practices and recommendations around code signing
#10
opened Aug 16, 2023 by
codeboten
Proposal: Use harden-runner in jobs using OPENTELEMETRYBOT_GITHUB_TOKEN
#74
opened Jun 22, 2023 by
pellared
[Proposal] Prefer GitHub-based security vulnerability reporting workflow
#75
opened Jan 18, 2023 by
yurishkuro
ProTip!
Add no:assignee to see everything that’s not assigned.