-
similar to sbom directory but all files will be in source tree (instead of generated like sbom are). The csaf files currently in /sbom will move to /csaf while the sbom files will stay in /sbom
-
Steps to reproduce:
- Star the backend with the latest version
- Upload all data from D1 https://github.com/trustification/trustify/tree/main/etc/datasets/ds1
- get the quarkus-sbom advisories usi…
-
We found a CSAF file that is ~100MB: https://access.redhat.com/security/data/csaf/v2/advisories/2018/rhsa-2018_3140.json
We will enlarge our restriction.
-
## Description
I would like to open a discussion regarding the file path convention for storing OpenVEX files within a Git repository. In the example of [Cilium](https://github.com/cilium/cilium/blob…
-
We would like the optional inclusion of the EPSS score of a vulnerability in the `scores` section within the `vulnerability properties` of a CSAF document.
-
Features to import/discuss:
- [ ] where should the examples live / repo structure
- [ ] separate the scheduler and the communication mechanism.
- [ ] RosMsgs
- [ ] ZMQ
- [ ] Compatibility with ex…
-
Each of the producer mostly has the same format or/and errors in validation, thus I pick just some examples
This was a manual testing with commit https://github.com/csaf-tools/CVRF-CSAF-Converter/c…
-
Dear GitHub team,
it would be nice, if your security advisories would also be available in the [Common Security Advisory Framework](https://docs.oasis-open.org/csaf/csaf/v2.0/csaf-v2.0.html). CSAF sp…
-
Taking the following example file: https://access.redhat.com/security/data/csaf/v2/advisories/2018/rhsa-2018_3140.json
For some of the tests, it takes quite a while:
```
Running: test: optional…
ctron updated
2 months ago
-