Hi @diego-gomez-olvera, I could say that UAST is in “active development state”. We don’t expect to produce incompatible changes to API (without notifications in advance at least), but there are still a lot of bugs (but it should become much better with Kotlin 1.2.20) and no documentation, guides or agreements about best practices. If you are going to use UAST for simple static checks - it is mainly ok, if you want to have something more interactive - it is more difficult. And yes you should be ready to build and learn it from sources.