neverland-cli
The todo command: a minimalist CLI to manage todos the GTD way, built for
fast daily use (fzf/gum for every interaction) and synchronized across devices
through a dedicated git repository. Part of
neverland.
Growing up means remembering deadlines. Neverland remembers them for you.
Install
pipx install neverland-cli # pulls neverland-core on its own
fzf is required (list selection); gum is optional (nicer prompts, falls back
to plain input when absent).
Quick start
todo init ~/todo-data # create/point at the git data repo
todo add "Call the plumber" # capture into the inbox, zero decisions
todo clarify # empty the inbox, one item at a time
todo next -c @computer # pick the next actions for a context
The command surface follows GTD's five steps (capture, clarify, organize, reflect, engage). See the main README for the full workflow and the domain model.
Metadata
Release files for neverland-cli 0.6.3
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 |
|---|---|---|---|---|
| neverland_cli-0.6.3.tar.gz | 16.8 kB | With provenance | Details for neverland_cli-0.6.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| neverland_cli-0.6.3-py3-none-any.whl | Python 3 | none | any | Details for neverland_cli-0.6.3-py3-none-any.whl |
Total release size: 33.7 kB
Release files / neverland_cli-0.6.3.tar.gz
| Download URL | neverland_cli-0.6.3.tar.gz |
|---|---|
| Size | 16.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
813ddc2f61c81ea36e23367df0f5bc739a8cfee1dc345a08257175127a18ecfc
|
|
BLAKE2b-256 checksum How to use checksums |
67c6e63c2dbfdfc89eb6f776e5b9bb7a0cd087a4e640d8e09e6f01719f8e5241
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Jul 23, 2026.
Transparency logRelease files / neverland_cli-0.6.3-py3-none-any.whl
| Download URL | neverland_cli-0.6.3-py3-none-any.whl |
|---|---|
| Size | 16.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ec68b6681a0c783cf4be81ff3de304f4ff6491e8704052031d1e98c3b71357af
|
|
BLAKE2b-256 checksum How to use checksums |
43b11e7b923436c47c787b90e5dbfcd475f01ff0b46af86833a5c576b3857156
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Jul 23, 2026.
Transparency logSecurity for neverland-cli 0.6.3
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 neverland_cli-0.6.3.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 Jul 23, 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.