Skip to content

Issues: ossf/malicious-packages

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

11 Open 9 Closed
11 Open 9 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Corrections Needed for Several Malware Attributions
#660 opened Oct 9, 2024 by behnazh-w
3
details formatting is incorrect and malformated
#579 opened Jul 11, 2024 by lukehinds
@calebbrown
2
Add Stacklok Trusty as a source, and allow access to AWS
#569 opened Jul 8, 2024 by lukehinds
2
fsevents <= 1.2.10 , is not malicious anymore
#527 opened Jun 9, 2024 by mustafanaa
1
Add an automated "impact" check
#517 opened Jun 5, 2024 by calebbrown
Entry for pytoileur is missing
#511 opened Jun 2, 2024 by prabhu
Add an automated check to ensure package reports are never removed.
#487 opened May 15, 2024 by calebbrown
Be more resilient to failures during preprocessing.
#430 opened Apr 5, 2024 by calebbrown
@calebbrown
Possible NPM false positives
#351 opened Feb 13, 2024 by maxfisher-g
Validate OSV against the ossf/osv-schema JSON schema.
#188 opened Oct 9, 2023 by calebbrown
4
Add docs for how to make use of the OSV reports
#110 opened Aug 10, 2023 by calebbrown
ProTip! Type g i on any issue or pull request to go back to the issue listing page.