Project Summary
LiquiBase is a DBMS-independent library for tracking, managing and applying database changes. It is built on a simple premise: All database changes (structure and data) are stored in an XML-based descriptive manner and checked into source control.
LiquiBase aims to provide a solution that:
* Supports merging of changes from multiple developers
* Works well with code branches
* Allows you to manage production data as well as various test datasets
* Works in an environment where multiple machines will be attempting to migrate the database concurrently
* Supports automated change-applying or generation of SQL scripts that can be approved and applied by a DBA
* Supports rolling back changes
* Database "diff" tool
In a Nutshell, LiquiBase...
- ...
- ...
-
...
has a well established, mature codebase
maintained by a very large development team
with decreasing Y-O-Y commits -
...
took an estimated 126 years of effort (COCOMO model)
starting with its first commit in February, 2007
ending with its most recent commit 5 days ago
MIT
Permitted
Commercial Use
Modify
Distribute
Place Warranty
Use Patent Claims
Forbidden
Sub-License
Hold Liable
Required
Distribute Original
Disclose Source
Include Copyright
State Changes
Include License
Include Install Instructions
These details are provided for information only. No information here is legal advice and should not be used as such.
Project Security
Vulnerabilities per Version ( last 10 releases )
There are no reported vulnerabilities
Project Vulnerability Report
Security Confidence Index
Vulnerability Exposure Index
Did You Know...
-
...
use of OSS increased in 65% of companies in 2016
-
...
check out hot projects on the Open Hub
-
...
nearly 1 in 3 companies have no process for identifying, tracking, or remediating known open source vulnerabilities
-
...
you can subscribe to e-mail newsletters to receive update from the Open Hub blog
30 Day SummaryMay 16 2025 — Jun 15 2025
|
12 Month SummaryJun 15 2024 — Jun 15 2025
|
