check-all-the-things VS gosec

Some links on these pages:

https://analysis-tools.dev/tag/rust https://github.com/mcandre/linters#rust https://github.com/collab-qa/check-all-the-things/blob/maste...

Myself and someone else built check-all-the-things, a tool that makes it easier to run various static analysis tools and other checks on a directory.

https://github.com/collab-qa/check-all-the-things

https://github.com/collab-qa/check-all-the-things/

6. Gosec

You can (and definitely should!) also use gosec.

The crypto source in Go is great, no complaints there. Lints like gosec even recommend using it when generating crypto entropy. Go did a good job here, and I expect Rust will do the same sometime after getrandom reaches 1.0 so the API questions are settled, plus whatever makes sense for the future-proofing the standard library needs.

i think there's https://github.com/securego/gosec linter

Various static analysis tools are available for the Go language, and existing static analysis tools can check general best practices. For example, gosec is a tool to check secure Go coding, and I use it myself. However, coding rules in software development are not only based on best practices, but can also be software- or team-specific. For example

What's the difference between this a https://github.com/securego/gosec?

A github actions workflow is provided to run go fmt, vet, test and gosec. An initial configuration for dependabot is also provided.

Besides what was mentioned, we use : staticcheck.io and https://github.com/securego/gosec

For application code, there are different SAST (Static Application Security Testing) tools like sonarqube, which provide vulnerability scanners for different languages, gosec for analyzing go code and detecting issues based on rules, linters, etc.