Disclaimer: I am currently NOT planning to remove support for CVSS v2. I know this should be a topic in the discussion tab (which is currently disabled), but since the topic can easily be closed (will not implement or implemeted), I decided to open an issue for this.
While working on CVSS v4.0 I noticed that the code includes some workarounds only for version 2 (e.g. has no unique string at the beginning, allows parentheses). These workarounds do not hinder me from adding new features, but I just wanted the check whether version 2 is still in use. If if turns out that version 2 is no longer used, I could clean up the code to improve the readabilitiy.
If a lot of people still rely on version 2, I will just keep everything as it is.
If I remove version 2, I will not include the changes in the next version. Maybe in the next major release or even later. This issue is only the see how people are working with version 2.
Disclaimer: I am currently NOT planning to remove support for CVSS v2. I know this should be a topic in the discussion tab (which is currently disabled), but since the topic can easily be closed (will not implement or implemeted), I decided to open an issue for this.
While working on CVSS v4.0 I noticed that the code includes some workarounds only for version 2 (e.g. has no unique string at the beginning, allows parentheses). These workarounds do not hinder me from adding new features, but I just wanted the check whether version 2 is still in use. If if turns out that version 2 is no longer used, I could clean up the code to improve the readabilitiy.
If a lot of people still rely on version 2, I will just keep everything as it is.
If I remove version 2, I will not include the changes in the next version. Maybe in the next major release or even later. This issue is only the see how people are working with version 2.
Best regards, Oliver