checks show
Last updated: April 29, 2026
Note: This is a Liquibase Secure feature, so you need a Liquibase Secure License Key to use it.
The checks show command prints the available checks and their configurations as indicated in the checks settings file to STDOUT.
Uses
You can use the checks show command to see the list of all available checks and inspect the dynamic checks.
Syntax
Run the command specifying your values:
liquibase checks show
Note: If you have a checks settings file customized for a specific environment or project, you need to pass that using the --checks-settings-file parameter. If you do not include this parameter, Liquibase uses the default settings file: liquibase.checks-settings.conf. See the Use the checks settings file article in the user guide for your product version.
The command output will present your checks and their details.
Parameters
Global parameters
Parameter | Definition | Requirement |
| Your Liquibase Pro license key | Required |
Command parameters
Parameter | Description | Requirement |
| Automatically enable new policy checks in | Optional |
| Allows automatic backup and updating of the | Optional |
| The name of the check(s) you want to target. Comma-separated list of one or more enabled checks. Checks to exclude can be prefixed with the | Optional |
| Only show the checks that are in the specified status. Valid values are | Optional |
| If using a checks packages file, optionally specify which packages should be run from the file as a comma-separated list. | Optional |
| Specifies the checks settings file to use with policy checks commands. Write the relative path of the settings file that you want to read from or modify. If the checks settings file is not present, you must also use | Optional |
| Liquibase 4.31.0+. If | Optional |
| Liquibase 4.31.0+. If | Optional |
| Only show the specified columns. Column options: | Optional |
Global parameters
Parameter | Definition | Requirement |
| Your Liquibase Pro license key | Required |
Command parameters
Parameter | Description | Requirement |
| Automatically enable new policy checks in | Optional |
| Allows automatic backup and updating of the | Optional |
| The name of the check(s) you want to target. Comma-separated list of one or more enabled checks. Checks to exclude can be prefixed with the | Optional |
| Only show the checks that are in the specified status. Valid values are | Optional |
| If using a checks packages file, optionally specify which packages should be run from the file as a comma-separated list. | Optional |
| Specifies the checks settings file to use with policy checks commands. Write the relative path of the settings file that you want to read from or modify. If the checks settings file is not present, you must also use | Optional |
| Liquibase 4.31.0+. If | Optional |
| Liquibase 4.31.0+. If | Optional |
| Only show the specified columns. Column options: | Optional |
Global parameters
Parameter | Definition | Requirement |
| Your Liquibase Pro license key | Required |
Command parameters
Parameter | Description | Requirement |
| Automatically enable new policy checks in | Optional |
| Allows automatic backup and updating of the | Optional |
| The name of the check(s) you want to target. Comma-separated list of one or more enabled checks. Checks to exclude can be prefixed with the | Optional |
| Only show the checks that are in the specified status. Valid values are | Optional |
| If using a checks packages file, optionally specify which packages should be run from the file as a comma-separated list. | Optional |
| Specifies the checks settings file to use with policy checks commands. Write the relative path of the settings file that you want to read from or modify. If the checks settings file is not present, you must also use | Optional |
| Liquibase 4.31.0+. If | Optional |
| Liquibase 4.31.0+. If | Optional |
| Only show the specified columns. Column options: | Optional |
Global parameters
Parameter | Definition | Requirement |
| Your Liquibase Pro license key | Required |
Command parameters
Parameter | Description | Requirement |
| Automatically enable new policy checks in | Optional |
| Allows automatic backup and updating of the | Optional |
| The name of the check(s) you want to target. Comma-separated list of one or more enabled checks. Checks to exclude can be prefixed with the | Optional |
| Only show the checks that are in the specified status. Valid values are | Optional |
| If using a checks packages file, optionally specify which packages should be run from the file as a comma-separated list. | Optional |
| Specifies the checks settings file to use with policy checks commands. Write the relative path of the settings file that you want to read from or modify. If the checks settings file is not present, you must also use | Optional |
| Liquibase 4.31.0+. If | Optional |
| Liquibase 4.31.0+. If | Optional |
| Only show the specified columns. Column options: | Optional |
Global parameters
Parameter | Definition | Requirement |
| Your Liquibase Pro license key | Required |
Command parameters
Parameter | Description | Requirement |
| Automatically enable new policy checks in | Optional |
| Allows automatic backup and updating of the | Optional |
| The name of the check(s) you want to target. Comma-separated list of one or more enabled checks. Checks to exclude can be prefixed with the | Optional |
| Only show the checks that are in the specified status. Valid values are | Optional |
| If using a checks packages file, optionally specify which packages should be run from the file as a comma-separated list. | Optional |
| Specifies the checks settings file to use with policy checks commands. Write the relative path of the settings file that you want to read from or modify. If the checks settings file is not present, you must also use | Optional |
| Liquibase 4.31.0+. If | Optional |
| Liquibase 4.31.0+. If | Optional |
| Only show the specified columns. Column options: | Optional |
Output
Starting Liquibase at 15:56:16 (version 4.19.0 #6648 built at 2023-01-17 15:02+0000) Liquibase Version: 4.19.0 Liquibase Open Source 4.19.0 by Liquibase Generating report on current configuration of checks using settings in: liquibase.checks-settings.conf
Short Name | Scope | Status | Severity | Customization | Description |
|---|---|---|---|---|---|
SqlGrantWarn | changelog | enabled | 0 | None | This check warns a user when SQL contains 'GRANT' statements so that they can ensure that the privilege being granted won't lead to security issues. |
SqlRevokeWarn | changelog | enabled | 0 | None | This check warns a user when SQL contains 'REVOKE' statements so that they can ensure that the privilege being revoked won't lead to data access and dependency issues. |
WarnOnUseDatabase | changelog | enabled | 0 | None | This check warns a user when generated or raw SQL contains 'USE DATABASE' directive. |
ChangeDropTableWarn | changelog | enabled | 0 | None | This check warns a user when a table is being dropped so that they can ensure that dropping the table won't lead to unintentional loss of data. |
ChangeDropColumnWarn | changelog | enabled | 0 | None | This check warns a user when a column is being dropped so that they can ensure that dropping the column won't lead to unintentional loss of data. |
ModifyDataTypeWarn | changelog | enabled | 0 | None | This check warns a user when a change will result in modification of a data type so they can ensure that modifying the data type won't lead to unintentional loss of data |
SqlSelectStarWarn | changelog | enabled | 0 | None | This check warns a user when generated or raw SQL contains 'SELECT *' statements so that they can ensure selecting all fields from a table in a query is safe and necessary |
SqlUserDefinedPatternCheck | changelog | disabled | 0 | SEARCH_STRING = null MESSAGE = A match for regular expression SEARCH_STRING was detected in Changeset CHANGESET. STRIP_COMMENTS = true | This check scans SQL for the presence of specific patterns and warns the user when they are found. |
TableColumnLimit | changelog, database | enabled | 0 | MAX_COLUMNS = 50 | Ensures that no table has more than a threshold number of columns. |
ObjectNameMustMatch | changelog, database | disabled | 0 | OPERATOR = STARTS_WITH SEARCH_STRING = null OBJECT_TYPES = null CASE_SENSITIVE = true | This check confirms the listed object names conform to the supplied pattern. |
ObjectNameMustNotMatch | changelog, database | disabled | 0 | OPERATOR = STARTS_WITH SEARCH_STRING = null OBJECT_TYPES = null CASE_SENSITIVE = true | This check confirms the listed object names do not match the supplied pattern. |
SqlGrantSpecificPrivsWarn | changelog | disabled | 0 | PRIVILEGE_LIST = null | This check warns a user when changeset includes or generates sql that grants specific privileges to a user or role |
ChangeTruncateTableWarn | changelog | enabled | 0 | None | This check warns a user when a table is being truncated so that they can ensure that truncating the table won't lead to unintentional loss of data. |
SqlGrantOptionWarn | changelog | enabled | 0 | None | This check warns a user when SQL contains 'GRANT' statements that include the 'WITH GRANT OPTION' clause so that they can ensure that the privilege being granted won't lead to security issues |
OracleReservedKeywords | changelog | disabled | 0 | OBJECT_TYPES = null ALLOWED_LIST = null CASE_SENSITIVE = true | Disallow Oracle reserved keywords from being used in database object names. See https://docs.oracle.com/cd/B19 306_01/em.102/b40103/app_oracl e_reserved_words.htm for complete list of keywords. |
SQLServerReservedKeywords | changelog | disabled | 0 | OBJECT_TYPES = null ALLOWED_LIST = null CASE_SENSITIVE = true | Disallow SQL Server reserved keywords from being used in database object names. See https://docs.microsoft.com/en- us/sql/t-sql/language-elements /reserved-keywords-transact-sq l?view=sql-server-ver16 for complete list of keywords. |
SQLServerFutureReservedKeywords | changelog | disabled | 0 | OBJECT_TYPES = null ALLOWED_LIST = null CASE_SENSITIVE = true | Disallow SQL Server's future reserved keywords from being used in database object names. See https://docs.microsoft.com/en- us/sql/t-sql/language-elements /reserved-keywords-transact-sq l?view=sql-server-ver16 for complete list of keywords. |
PostgresReservedKeywords | changelog | disabled | 0 | OBJECT_TYPES = null ALLOWED_LIST = null CASE_SENSITIVE = true | Disallow Postgres reserved keywords from being used in database object names. See https://www.postgresql.org/doc s/14/sql-keywords-appendix.htm l for complete list of keywords. |
SQLServerODBCReservedKeywords | changelog | disabled | 0 | OBJECT_TYPES = null ALLOWED_LIST = null CASE_SENSITIVE = true | Disallow SQL Server's ODBC reserved keywords from being used in database object names. See https://docs.microsoft.com/en- us/sql/t-sql/language-elements /reserved-keywords-transact-sq l?view=sql-server-ver16 for complete list of keywords. |
PostgresNonReservedKeywords | changelog | disabled | 0 | OBJECT_TYPES = null ALLOWED_LIST = null CASE_SENSITIVE = true | Disallow Postgres non-reserved keywords from being used in database object names. See https://www.postgresql.org/doc s/14/sql-keywords-appendix.htm l for complete list of keywords. |
SqlGrantAdminWarn | changelog | enabled | 0 | None | This check warns a user when SQL contains 'GRANT' statements that include the 'WITH ADMIN OPTION' clause so that they can ensure that the privilege being granted won't lead to security issues |
DetectChangeType | changelog | enabled | 0 | CHANGE_TYPE_LIST = dropTable,dropColumn | This check warns a user when a ChangeSet includes a ChangeType listed by the user as forbidden |
RollbackRequired | changelog | enabled | 0 | None | This check triggers when a changeset does not have a rollback defined. |
ChangesetLabelCheck | changelog | enabled | 0 | None | This check enforces the Liquibase recommendation that labels be assigned to each changeset to provide better deployment control and to enhance traceability of efforts across changesets. |
ChangesetContextCheck | changelog | enabled | 0 | None | This check enforces the Liquibase recommendation that contexts be assigned to each changeset to provide better deployment control and to enhance traceability of efforts across changesets. |
ChangesetCommentCheck | changelog | enabled | 0 | None | This check enforces the Liquibase recommendation that comments be added to each changeset to document the purpose of a changeset for other/future consumers of this changelog |
PrimaryKeyOnCreateTable | changelog | enabled | 0 | EXCEPTIONS_LIST = CASE_SENSITIVE = true | This check warns when a create table action doesn't also include a primary key. |
CheckTablesForIndex | database | enabled | 0 | None | This check scans your target URL database tables to find tables which do not have an associated index. |
TableCommentCheck | database | disabled | 0 | None | This database check flags any table which does not have a comment. (Note: This is not a check for a Liquibase changelog comment.) |
TableCommentPatternCheck | changelog, database | disabled | 0 | OPERATOR = CONTAINS SEARCH_STRING = null MESSAGE = A match for regular expression SEARCH_STRING was detected in IDENTIFIER. | This check triggers when specific user-supplied patterns are found in Table Comments. |
ConstraintMustExist | database | disabled | 0 | CONSTRAINT_OPERATOR = STARTS_WITH TABLE_NAME = null COLUMN_NAME = null CONSTRAINT = PRIMARYKEY CASE_SENSITIVE = true MESSAGE = The specified table 'TABLE_NAME' does not contain the required 'CONSTRAINT' constraint. | Check for and alert when specified table does not contain the required constraint(s). |
RequireChangesetIDisUUID | changelog | disabled | 0 | None | Alerts when a changeset ID does not follow the 8-4-4-4-12 pattern of UUID or GUID. |
INFO: Customize 'checks show' table with --show-cols flag. Learn more with 'liquibase checks show --help' Liquibase command 'checks show' was executed successfully.