Static Code Analyzer for Elixir

1. Do not operate on Elixir code per se, but on abstract terms (beam_lib, BEAM Wisdoms and The BEAM Book). This will not require expanding macros or other Elixir magic. Additionally it will allow you to use the same code for other BEAM languages.
2. Check out Concuerror for concurrency testing; Elvis and Credo for static analysis (mostly linting in that case, but the same rules will mostly apply to other analysers). You can also check Dialyzer code and Gradualizer for type checkers.
3. While I see possibilities in concurrency checkers I hardly see how you would be able to find “memory” issues in BEAM (unless you want to find them in the VM itself), as GC will mostly take care of it for you. The only “problems” I can see is in case if you would parse large binaries and then store the parts as the refs (see Jason.decode/2 :strings option for example). Other than that it is in reality finding long-running processes with large state.

You should understand Philip Wadler’s attempt to statically type Erlang in 2002. Wadler: Erlang