Add ThreatCrush CI workflow (staged at docs/ pending rename) - #2
Merged
Conversation
The file belongs at .github/workflows/threatcrush-scan.yml. It is staged here because the pushing token lacks the `workflow` OAuth scope; GitHub blocks any token-based write to .github/workflows/. Rename this file in the GitHub web UI to move it into place. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ralyodio
added a commit
that referenced
this pull request
Aug 1, 2026
Relocates the workflow staged at docs/threatcrush-scan.yml in #2 to the path GitHub Actions actually reads. No content change. Co-authored-by: Claude <noreply@anthropic.com>
ralyodio
added a commit
that referenced
this pull request
Aug 1, 2026
Staged outside .github/workflows/ because the pushing token lacked the workflow OAuth scope. Moved into place in #3. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
ralyodio
added a commit
that referenced
this pull request
Aug 1, 2026
Relocates the workflow staged in #2 to the path GitHub Actions reads. No content change. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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 file belongs at .github/workflows/threatcrush-scan.yml. It is staged here because the pushing token lacks the
workflowOAuth scope; GitHub blocks any token-based write to .github/workflows/. Rename this file in the GitHub web UI to move it into place.Test Case Submission
docs/CONTRIBUTING.mdif (false),if False:,NEVER_RUN, …).invalid,.example,example.com)@id,@cwe,@severity,@language,@expected-detection,@description,@safe-guard)VULNERABLE:and any correct-code lines withSAFE:scripts/validate-test-case.shand it passedpython3 scripts/generate-catalog.py) and committed the resultDetails
Safety statement
Explain, in your own words, why this submission cannot cause harm if someone
checks it out and runs the repository. Point at the specific guard.
Scanner result
Leave blank on submission — CI fills this in. After the run, confirm whether
ThreatCrush detected the case and note any surprise (missed detection, or a
SAFE:line flagged).