As mentioned in https://github.com/csaf-poc/csaf_distribution/issues/367, we are currently trying to integrate this repository into our Clouditor open-source cloud security solution (see https://github.com/clouditor/clouditor/issues/1414 for more information). Basically, we could make use of the csaf_provider (for testing) as well as the csaf_checker to perform and integrate conformance checks. However, currently, the majority of the code of both resides in the main package, making it impossible to use from an external source.
I would therefore propose to move everything except the main.go out of the respective main packages. This would then result in a folder structure similar to this:
As mentioned in https://github.com/csaf-poc/csaf_distribution/issues/367, we are currently trying to integrate this repository into our Clouditor open-source cloud security solution (see https://github.com/clouditor/clouditor/issues/1414 for more information). Basically, we could make use of the
csaf_provider
(for testing) as well as thecsaf_checker
to perform and integrate conformance checks. However, currently, the majority of the code of both resides in themain
package, making it impossible to use from an external source.I would therefore propose to move everything except the
main.go
out of the respectivemain
packages. This would then result in a folder structure similar to this:What do you think?