docs(security): Add current security review evidence#8584
Merged
jkowall merged 2 commits intoMay 17, 2026
Conversation
Signed-off-by: Jonah Kowall <jkowall@kowall.net>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds current public security review evidence for Jaeger’s OpenSSF Best Practices Gold security_review criterion and updates existing security documentation to reference it.
Changes:
- Adds a 2026 security review artifact covering reviewed inputs, requirements, boundaries, and follow-up cadence.
- Updates
SECURITY.mdand the OpenSSF Gold evidence tracker to link to the new review. - Removes
security_reviewfrom remaining Gold work items.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
SECURITY.md |
Adds the 2026 security review to the security documentation index. |
docs/security/security-review-2026.md |
Introduces the public security review evidence artifact. |
docs/security/openssf-gold-evidence.md |
Updates review date, points security_review evidence to the new artifact, and removes it from pending work. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Add Self-Assessment and CI security workflows to Inputs Reviewed, add Reviewers row to metadata, separate authentication from authorization in Access control row, and link CodeQL/dependency-review/ Scorecard/FOSSA workflows from Vulnerability handling and Supply-chain rows. Signed-off-by: Jonah Kowall <jkowall@kowall.net>
jkowall
force-pushed
the
codex/openssf-security-review-8485
branch
from
42b6315 to
2c5961d
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #8584 +/- ##
=======================================
Coverage 96.53% 96.53%
=======================================
Files 330 330
Lines 17363 17363
=======================================
Hits 16762 16762
Misses 453 453
Partials 148 148
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
yurishkuro
approved these changes
May 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
security_reviewcriterionSECURITY.mdto point at the new reviewRefs #8485.
Refs #8481.
Validation
make fmtmake lintmake testFollow-up
After this lands, update the OpenSSF Best Practices BadgeApp
security_reviewevidence URL tohttps://github.com/jaegertracing/jaeger/blob/main/docs/security/security-review-2026.md.