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
Some end users have applications that automatically parse a CNAsList.json file from https://github.com/CVEProject/cve-website to obtain information about CNAs. A URL corresponding to the default branch - specifically https://raw.githubusercontent.com/CVEProject/cve-website/dev/src/assets/data/CNAsList.json - was usable until early March 2024. However, this has not been updated recently, and all consumers of CNAsList.json apparently should be using https://raw.githubusercontent.com/CVEProject/cve-website/main/src/assets/data/CNAsList.json today instead.
Forums where CNAsList.json was previously "advertised" or discussed, e.g., working groups or Slack, may not have seen an announcement of this change.
The text was updated successfully, but these errors were encountered:
Note: a solution for where this information should live is being discussed here: CVEProject/automation-working-group#133
Sorry, something went wrong.
No branches or pull requests
Some end users have applications that automatically parse a CNAsList.json file from https://github.com/CVEProject/cve-website to obtain information about CNAs. A URL corresponding to the default branch - specifically https://raw.githubusercontent.com/CVEProject/cve-website/dev/src/assets/data/CNAsList.json - was usable until early March 2024. However, this has not been updated recently, and all consumers of CNAsList.json apparently should be using https://raw.githubusercontent.com/CVEProject/cve-website/main/src/assets/data/CNAsList.json today instead.
Forums where CNAsList.json was previously "advertised" or discussed, e.g., working groups or Slack, may not have seen an announcement of this change.
The text was updated successfully, but these errors were encountered: