Static code Analysis for ChangeSets?

Liquibase Development
1

Are there any plans regarding static analysis of the changesets? I am aware of liquibase-linter and of the features available in the pro version, but those do not cover my use case. The rules I have in mind are along the lines of ‘every table/index should have a tablespace’ or ‘in case a variable is used, is said variable populated in advance?’. Those checks can and should be done before deployment, I am therefore looking for a solution that does not connect to the target database and it should be usable in a unit-test (not only via the maven-plugin).
In case I implement an open-source/free solution myself, at what point would I be infringing on your copyright? By referring to the name ‘liquibase’ ?