First of all: kube-score is an awesome project! Thanks for all your efforts!

I would like to use kube-score more in a library/'framework' way as part of an internal project to provide best practice reports to our Kubernetes teams.

Therefore some additional features would come in handy:

1. the current Score function only takes a configuration struct. To be able to use kube-score as library it would be nice to be able to pass the *checks.Checks as parameter to be able to add custom checks that only apply to our environment.
2. rather a mid/long-range feature: support for arbitrary CRDs would allow us/everyone to add custom checks for CRDs like Cilium, Prometheus, Velero,... or even their own. To support this I think an architecture change how the data is collected and passed to the checks could be necessary but it would probably also make it easier to extend kube-score in the future.

I'd have a rough idea how to achieve all this but I figured it would be better to first ask you what you think, is this something you'd be interested in? Shall I just create a PR(s) and we discuss further details directly in these?