Looks like an interesting toolkit to make your own code checkers.

Improved static analysis for C straight from GCC. This is definitely welcome.

Long but fascinating article on a blend of guidelines which could be statically checked to enforce a memory-safe subset of C++.

Really nice little tool, this is indeed surprising how little code is needed for something like this. Treesitter is definitely a huge help there.

Interesting approach. There's still a lot we can achieve with static analysis in those good old languages.

Looks like an interesting (even though young) tool to make your own linters and to analyze code source.

Bunch of good advice. In a way it boils down to: name things properly and use static analysis tools extensively. Still, couple of nice operational guidelines which work in most languages.

Looks like an interesting static analyzer, I guess I'll try to use it on a couple of projects.