Vijay Sarvepalli

> Hi, thank you for attempting to provide a workaround, but: > > 1. it would only be a workaround, so I'd recommend that the code is fixed to deal...

Hello @abhraj26 Can you please send an email to [email protected]? I don't think this is a software bug. It is more an operational scenario - it is likely your account...

Look at the demo work current in progress and related discussion https://github.com/CERTCC/SSVC/discussions/649 [https://democert.org/ssvc/simple/](https://democert.org/ssvc/simple/) An implementation of CVSS v4 exists there in the demo, however it has only the "lookup" functionality...

Yeh I see a different use case of evaluations being done from mapping CVSS metrics to SSVC. The discussions so far has been customizing SSVC tree in the tool itself....

Some of the files in the data/json folder are not quite correct for example https://github.com/CERTCC/SSVC/blob/main/data/json/decision_points/cvss/availability_impact_2_0_1.json should be version `3.0.0` (There is NO Version `2.0.1` in the code) https://github.com/CERTCC/SSVC/blob/2bea679ead3502b5a9a8435e01dcd10b47cfee04/src/ssvc/decision_points/cvss/availability_impact.py#L122 I think...

I am hoping enumerating this properly will get rid of this type of inconsistencies.

Yeh resolved. We can close this.

Hey @dosu bot It looks like this issue got fixed with some import restrictions that were put in place in the latest code. Can you confirm that? Is it possible...

Hello @ziadhany Thanks for catching this. It is from the earlier definition of Virulence that needs to be fixed. We will take care of the clean up soon. Also need...

Hello @tschmidtb51 It does not impact CSAF. As each CSAF vulnerability report can copy and include multiple vulnerabilities with its own container. So there is no concern there. The use...