Is Dough using static analysis to find bugs in its firmware?

Nvidia uses Coverity to find bugs in its driver:

There are also free static analyzers such as Clang’s static analyzer, clang-tidy and cppcheck. Coincidentally, all three can be used via Ericsson’s CodeChecker:

Is Dough using any static analysis tools to try to find bugs in its firmware?

As a corollary question, is Dough building with -Werror and fixing the issues that the compiler reports? Leaving those reports unfixed can often hide actual issues in the code.

Projects that use static analysis tend not to have as many issues as Dough’s monitor firmware seems to have, so it occurred to me that perhaps Dough is not using static analysis tools.