chore: refresh security-insights.yml metadata#177
Merged
Conversation
The repo's own security-insights.yml had drifted: the URLs referenced the pre-rename `ossf/security-insights-spec` repo (now redirects), last-updated/last-reviewed dates were 16+ months stale, schema-version was pinned to 2.0.0 while the project is at 2.2.0, and the self assessment evidence URL pointed at a docs/threat-model directory that does not exist in this repo. Drop the dangling evidence URL and bring URLs, dates, and schema-version current. Signed-off-by: Eddie Knight <knight@linux.com>
jmeridth
approved these changes
May 8, 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
2 participants
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.
The repo's own security-insights.yml had drifted: the URLs referenced the pre-rename
ossf/security-insights-specrepo (now redirects), last-updated/last-reviewed dates were 16+ months stale, schema-version was pinned to 2.0.0 while the project is at 2.2.0, and the self assessment evidence URL pointed at a docs/threat-model directory that does not exist in this repo. Drop the dangling evidence URL and bring URLs, dates, and schema-version current.