SQLCipher is an open source project, below are a few resources for those interested in the community behind the project. Digital signatures for community releases can be found here.
The source code for the core SQLCipher library can be found here, or can be cloned from our git repository:
git clone https://github.com/sqlcipher/sqlcipher.gitSource code for the Android packages are made available via git:
git clone https://github.com/sqlcipher/sqlcipher-android.gitNote that private support for SQLCipher is available through our Commercial Edition program.
For those using the Open Source Community Edition software, the primary venue for free support and announcements is the SQLCipher discussion site. This resource provides a searchable forum where community members can come together to ask questions and get answers about SQLCipher.
All Open Source requests should initially be opened in the community discussion site! GitHub issues are reserved for reproducible bug reports, and we are unable to provide private support for Community Edition users.
Bug reports for specific issues in SQLCipher should be reported to the project GitHub Issues Page. Note that only legitimate reproducible bugs should be filed on the GitHub page; if you're not sure, please post to the discuss site first!
The SQLCipher project also welcomes Pull Requests. Please note that a current contributor license agreement is required before any patches will even be looked at for consideration.
SQLCipher Community Edition can be used it in both open source and closed source commercial software, but you must include our BSD-style license and copyright statements prominently in the application and documentation.
When you include SQLCipher Community Edition in your project, you must comply with the BSD-style license terms. The most important requirement is that you must reproduce the copyright notice, license conditions, and disclaimer in your application.
The SQLCipher Community Edition license requires that you include the following in a user-accessible location:
The license and copyright statements must be included in a location that is accessible to users. Acceptable locations include:
Example: A mobile application might include a "Settings > About > Open Source Licenses" screen that displays the SQLCipher copyright and license text along with other open source components used in the application.
If you create modified versions, builds, or extensions of SQLCipher and distribute them to others, there are important trademark considerations in addition to license compliance.
SQLCipher is a registered trademark of Zetetic, LLC. Forks, modified versions, or redistributions of SQLCipher by third parties should not use the name "SQLCipher" directly as the primary product name. This helps avoid confusion among users about the source and support status of the software.
When creating a fork or distribution of SQLCipher, you should use one of the following approaches:
Add your project, package, or organization name before "SQLCipher" to clearly distinguish it from the official releases.
Choose a completely different name that does not include "SQLCipher" to avoid any potential confusion.
Even when using a different name, your documentation should clearly state that your project is based on or derived from SQLCipher, and must include the required copyright and license notices. For example:
MyProject-SQLCipher is a modified distribution of SQLCipher. SQLCipher is Copyright (c) 2008-2024, ZETETIC, LLC and is used under the terms of the BSD-style license.