openssl / openssl/release-metadata
Check secadv/ against secjson/, and fix the latter where necessary
Open
@mattcaswell is already working on this.
Since May 7, 2025.
- Dominant language
- No language data
- Stars
- 3
- Forks
- 6
- Avg merge
- 19m
- Merged PRs (30d)
- 1
Description
It appears that some of the JSON entries lack data that's present in the advisory texts
A few examples, taken from openssl/openssl#27577:
- secjson/CVE-2023-0215.json is missing attributions present in secadv/20230207.txt
- secjson/CVE-2023-1255.json is missing attributions present in secadv/20230420.txt, and has an incorrect advisory text URL.
- secjson/CVE-2022-0778.json is missing attributions present in secadv/20220315.txt
- secjson/CVE-2021-3712.json is missing attributions present in secadv/20210824.txt
We need to go through all advisories, at least recent enough, to check that data matches, and fix the JSON data where there's a difference (we do assume that the advisory text files are correct records).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.