New Published Rules - p0_security.direct-response-write-copy #3382
Conversation
This file contains 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
![semgrep-dev-pr-bot[bot]](https://avatars.githubusercontent.com/in/60337?s=60&v=4){kind=small}
|
I couldn't figure out how to make a PR directly to the source rule from the online editor. Clicking "publish" as an outside contributor on a diff to an existing rule from the editor yields a "fatal error" screen. Therefore, these code files are in the wrong location (should be in Anyway, this rule code appears to work. Fixes #3381 |
|
@nbrahms Hey! thanks for the update! I added your fix to the original rule 👍 |
inkz
approved these changes
May 9, 2024
3 tasks
Yay thank you! |
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.
Wahoo! New published rules with
p0_security.direct-response-write-copyfrom @nbrahms.See semgrep.dev/s/PeodN for more details.
Thanks for your contribution! ❤️