csaf_distribution
csaf_distribution copied to clipboard
csaf-poc
Tools to download or provide CSAF (Common Security Advisory Framework) documents.
The library needs proper documentation. This includes a [README](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes) that describes the library, its functions and use cases. The documentation of all functions also must happen automatically on release via...
As defined via https://docs.oasis-open.org/csaf/csaf/v2.0/os/csaf-v2.0-os.html#31232-branches-type---name-under-product-version-range. The go-library should be able to test a string representing a version range for validity and create a valid version-range-representing string. This would e.g. allow it...
Specifically, given a csaf-document via a structure as defined via https://github.com/csaf-poc/csaf_distribution/issues/559, the library is supposed to be able to - [ ] add elements - [ ] edit elements or...
This issue depends on https://github.com/csaf-poc/csaf_distribution/issues/559. Any csaf-document should be able to be read into that go-structure, and any go-structure should be able to be saved or exported as csaf-document. This...
This should help support https://github.com/csaf-poc/csaf_distribution/issues/367 The idea is that if anything is a Csaf-advisory, then it can be represented completely via this structure. https://docs.oasis-open.org/csaf/csaf/v2.0/os/csaf-v2.0-os.html contains the specifications for how the...
We get an error after upgrading to 3.2.0 that `csaf.HashedAdvisoryFile` is gone? I was not expecting this in the same major version. Was this intended? See https://github.com/clouditor/clouditor/pull/1691
This adds a check to the canonical URL prefix configuration. It detects if an error occurs when the user specifies an invalid URL. This is a breaking change, as an...
> This affects the canonical URLs in the `csaf_provider` as well. _Originally posted by @tschmidtb51 in [#630](https://github.com/gocsaf/csaf/issues/630#issuecomment-2759120645)_
Currently, there are some linter warnings about the naming of struct fields: ``` csaf/advisory.go:449:2: struct field ProductIds should be ProductIDs csaf/advisory.go:612:2: struct field GroupIds should be GroupIDs csaf/advisory.go:613:2: struct field...