Alternatives to Go Report Card

[bcdxn]

It looks like Go Report Card has been sunset without a clear alternative. The contributing guide still mentions Go Report Card requirements in the PR "Quick Checklist" section: https://github.com/avelino/awesome-go/blob/main/CONTRIBUTING.md?plain=1#L39

Are there strong opinions on what Awesome Go contributions should require going forward? I'm happy to clean up the documentation and submit a PR if the community can come to a decision on a replacement.

Go Report Card itself points to golangci-lint for linting and formatting. I'd also throw in a vote for something like meeting the baseline requirements in the OpenSSF Best Practices project (as shown on oapi-codegen's README, for example), though it is a bit more manual than Go Report Card.

P.S. Go Report Card, you will be missed!

[screwyprof]

golangci-lint is a very good alternative. Problem is it has very many linters and tons of settings, so the question is which one should be the baseline?

I've a coverage tool I build and thinking about suggesting it to this repo and now I'm confused as whether to add goreport card to play the CI checks or hold on for a resolution of this issue first? I've got 69 active linters, property tests, mutation tests and other less common quality gates in my pipeline. I wish there were free reliable quality gates to integrate with to get a nice badge, but alas nothing comes to my mind. Most of the platforms I've seen basically run golangci-lint for golang projects and that's it.