litecli
A command-line client for SQLite databases that has auto-completion and syntax highlighting.
Installation
If you already know how to install python packages, then you can install it via pip:
You might need sudo on linux.
$ pip install -U litecli[sqlean]
For MacOS users, you can also use Homebrew to install it:
$ brew install litecli
Usage
$ litecli --help
Usage: litecli [OPTIONS] [DATABASE]
Examples:
- litecli sqlite_db_name
A config file is automatically created at ~/.config/litecli/config at first launch. For Windows machines a config file is created at ~\AppData\Local\dbcli\litecli\config at first launch. See the file itself for a description of all available options.
Docs
Visit: litecli.com/features
1 maintainer
Metadata
1 maintainer
Release files for litecli 1.17.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| litecli-1.17.1.tar.gz | 900.3 kB | With provenance | Details for litecli-1.17.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| litecli-1.17.1-py3-none-any.whl | Python 3 | none | any | Details for litecli-1.17.1-py3-none-any.whl |
Total release size: 957.4 kB
Release files / litecli-1.17.1.tar.gz
| Download URL | litecli-1.17.1.tar.gz |
|---|---|
| Size | 900.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e2f7191eaba830b24dbbfc9171a495c62562df923ba1cc3b2db2652547c1bac8
|
|
BLAKE2b-256 checksum How to use checksums |
e3d5afec99cc3eaba96214d77e76438d7fe5e6ea54704b0e47dd97d9696ccd6c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 31, 2026.
Transparency logRelease files / litecli-1.17.1-py3-none-any.whl
| Download URL | litecli-1.17.1-py3-none-any.whl |
|---|---|
| Size | 57.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4d1743dfa086b178de6543b36f1780203e8a9bc99643af4b721f6c880c5aa7a9
|
|
BLAKE2b-256 checksum How to use checksums |
dba12221a671b7f7bca22d72beca6bfa14ee252f3a4d08272bece10ed96cc2f5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 31, 2026.
Transparency logSecurity for litecli 1.17.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for litecli-1.17.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 31, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
