# Static code Analysis for ChangeSets?

**URL:** https://forum.liquibase.org/t/static-code-analysis-for-changesets/8555
**Category:** Liquibase Development
**Created:** [August 18, 2023, 7:42am UTC](https://forum.liquibase.org/t/static-code-analysis-for-changesets/8555 "2023-08-18T07:42:19Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![ralferic](https://avatars.discourse-cdn.com/v4/letter/r/df788c/32.png) [@ralferic](https://forum.liquibase.org/u/ralferic)
#### Post date: [August 18, 2023, 7:42am UTC](https://forum.liquibase.org/t/static-code-analysis-for-changesets/8555/1 "2023-08-18T07:42:19Z")

</div>

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’ ?