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
cve
safety-db/data/insecure_full.json
Line 2640 in c4f4673
The value for cve there should probably be null .
null
The text was updated successfully, but these errors were encountered:
Thanks, fixed. Note that this would not update to our free database until October 1st.
Sorry, something went wrong.
FYI we have code/tests to detect such issues https://github.com/nexB/vulnerablecode/blob/e65ac68177dd41eaae9a79914712bac00058e0aa/vulnerabilities/importers/safety_db.py#L51
If you are interested I could file a PR to include a schema test as a part of CI.
Thanks for that link. We're actually about to include some server-side code that will sanitize the CVE value on our end.
No branches or pull requests
safety-db/data/insecure_full.json
Line 2640 in c4f4673
The value for cve there should probably be
null
.The text was updated successfully, but these errors were encountered: