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.
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
Generic pipeline for importing Vulnerabilities. #44
Labels
Comments
oliverchang
added a commit
that referenced
this issue
Feb 2, 2021
OSS-Fuzz vulnerabilities are exported to a git repository, where users can make manual changes/corrections if necessary. These changes will flow back into OSV. Part of generic importer pipeline (#44).
oliverchang
added a commit
that referenced
this issue
Feb 2, 2021
OSS-Fuzz vulnerabilities are exported to a git repository, where users can make manual changes/corrections if necessary. These changes will be imported back into OSV. Part of generic importer pipeline (#44).
oliverchang
added a commit
that referenced
this issue
Feb 2, 2021
OSS-Fuzz vulnerabilities are exported to a git repository, where users can make manual changes/corrections if necessary. These changes will be imported back into OSV. Part of generic importer pipeline (#44).
This was referenced Feb 8, 2021
Closed
|
This may be a duplicate? |
oliverchang
added a commit
that referenced
this issue
Feb 16, 2021
oliverchang
added a commit
that referenced
this issue
Feb 17, 2021
- Start plumbing for detecting user changes and kicking off analysis tasks. - Don't make empty commits when importing new OSS-Fuzz entries. Part of #44.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Extend the current OSS-Fuzz pipeline to support generic data sources.
More requirements:
Current sketch (subject to change):
The text was updated successfully, but these errors were encountered: