📖 Add Security Insights file and update maintainer affiliation - #4863
Merged
Conversation
justaugustus
requested review from
AdamKorcz and
raghavkaul
and removed request for
a team
November 25, 2025 02:46
justaugustus
temporarily deployed
to
integration-test
November 25, 2025 02:46 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
dosubot
Bot
added
the
size:M
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4863 +/- ##
==========================================
+ Coverage 66.80% 69.59% +2.78%
==========================================
Files 230 251 +21
Lines 16602 15657 -945
==========================================
- Hits 11091 10896 -195
+ Misses 4808 3891 -917
- Partials 703 870 +167 🚀 New features to boost your workflow:
|
spencerschrock
approved these changes
Nov 25, 2025
Signed-off-by: Stephen Augustus <foo@auggie.dev>
Some security analysis tools leverage security-insights.yml to infer information about a project, so we add it here. Signed-off-by: Stephen Augustus <foo@auggie.dev>
justaugustus
temporarily deployed
to
integration-test
November 25, 2025 16:02 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
justaugustus
enabled auto-merge (squash)
November 25, 2025 16:05
thomasleplus
pushed a commit
to thomasleplus/scorecard
that referenced
this pull request
Mar 8, 2026
…4863) - MAINTAINERS: Update Jeff's affiliation - .github: Add security-insights.yml Some security analysis tools leverage security-insights.yml to infer information about a project, so we add it here. --------- Signed-off-by: Stephen Augustus <foo@auggie.dev>
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.
What kind of change does this PR introduce?
(Is it a bug fix, feature, docs update, something else?)
Follow-up to #4862, as the OSPS Baseline assessment GitHub Action uses security-insights.yml as input.
What is the current behavior?
What is the new behavior (if this is a feature change)?**
Which issue(s) this PR fixes
Special notes for your reviewer
Note that this is an intentionally minimally viable security-insights.yml. We'll add on top of the MVP post-merge.
Does this PR introduce a user-facing change?
For user-facing changes, please add a concise, human-readable release note to
the
release-note(In particular, describe what changes users might need to make in their
application as a result of this pull request.)