This repository was archived by the owner on Aug 26, 2025. It is now read-only.
Merged
Conversation
furi0us333
suggested changes
Feb 10, 2025
Contributor
furi0us333
left a comment
furi0us333
left a comment
There was a problem hiding this comment.
I talked to research and we have reasonable confidence in the OSV data, so I think it makes sense to add it to this policy. However, I am noticing now that the original tag/metadata is incorrect. CM0037 is actually the malware binary and CM0038 is the verified malware. Can you please include the new tag with CM0038 and fix the metadata in this PR?
Contributor
|
Will we need to do anything to cause this to update across the platform? |
Contributor
Author
|
Yes, because we never completed #8 somebody will need to run the deployment manually. |
furi0us333
approved these changes
Feb 10, 2025
Contributor
Author
|
Deployed on prod: |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Since the latest release of the API, if a package is marked as malware by the OSSF MAL database we add an issue with a CM1002 tag. This has roughly the same meaning as CM0037, our internal tag for when we've marked something as malware, so I put it into the same rule.