We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://github.com/google/vanir is a system for
This seems very useful for the general C/C++ ecosystem, where vendoring/forking is very common. Today, our approach is to guess the closest upstream repository (tagged) commit, and key vulnerability matching based on vulnerable commit ranges (https://osv.dev/blog/posts/introducing-broad-c-c++-support/)
Vanir seems like an alternative approach that could work better.
@baekhyunwook
The text was updated successfully, but these errors were encountered:
This issue has not had any activity for 60 days and will be automatically closed in two weeks
See https://github.com/google/osv-scanner/blob/main/CONTRIBUTING.md for how to contribute a PR if you're interested in helping out.
Sorry, something went wrong.
No branches or pull requests
https://github.com/google/vanir is a system for
This seems very useful for the general C/C++ ecosystem, where vendoring/forking is very common. Today, our approach is to guess the closest upstream repository (tagged) commit, and key vulnerability matching based on vulnerable commit ranges (https://osv.dev/blog/posts/introducing-broad-c-c++-support/)
Vanir seems like an alternative approach that could work better.
@baekhyunwook
The text was updated successfully, but these errors were encountered: