Remove scan_memory_yara from default actions
#169
Merged
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
CRefice
approved these changes
Nov 24, 2025
Collaborator
CRefice
left a comment
CRefice
left a comment
There was a problem hiding this comment.
Fair. Maybe this is a good enough reason to also implement that scan_memory_regex action we were talking about.
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.
yara-xis super heavy create that significantly increases the compilation time, inflates the binary size and brings dependency onwasmtimethat does somecchackery that completely breaks cross-compilation capabilities.I think it is better to remove it from default actions and make it an opt-in.