🐛 detect blocked user name and email in dangerous workflow #4720
Conversation
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
AdamKorcz
requested review from
spencerschrock and
raghavkaul
and removed request for
a team
AdamKorcz
temporarily deployed
to
integration-test
GitHub Actions
Inactive
AdamKorcz
force-pushed
the
dwf-blocked-user
branch
from
765c0a0 to
c849a89
Compare
AdamKorcz
temporarily deployed
to
integration-test
GitHub Actions
Inactive
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4720 +/- ##
==========================================
+ Coverage 66.80% 68.30% +1.49%
==========================================
Files 230 249 +19
Lines 16602 18900 +2298
==========================================
+ Hits 11091 12909 +1818
- Misses 4808 5131 +323
- Partials 703 860 +157 🚀 New features to boost your workflow:
|
Signed-off-by: Adam Korczynski <[email protected]>
AdamKorcz
force-pushed
the
dwf-blocked-user
branch
from
c849a89 to
0fb1c49
Compare
AdamKorcz
temporarily deployed
to
integration-test
GitHub Actions
Inactive
|
This pull request has been marked stale because it has been open for 10 days with no activity |
spencerschrock
approved these changes
Aug 12, 2025
|
This pull request has been marked stale because it has been open for 10 days with no activity |
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.
What kind of change does this PR introduce?
(Is it a bug fix, feature, docs update, something else?)
feature
What is the current behavior?
Scorecard doesn't detect use of blocked_user name and email. These are values controlled by users and can be weaponized. I am not sure an email can be weaponized, but Scorecard detects these in other cases, so I am adding that too.
See details in https://docs.github.com/en/webhooks/webhook-events-and-payloads#org_block
What is the new behavior (if this is a feature change)?**
Scorecard detects use of blocked_user name and email.
Which issue(s) this PR fixes
NONE
Special notes for your reviewer
I have not found any examples of this in any open source project, but from what I can read from https://docs.github.com/en/webhooks/webhook-events-and-payloads, it is a field that can exist in events.
Does this PR introduce a user-facing change?
For user-facing changes, please add a concise, human-readable release note to
the
release-noteYes