Stanwell
Have enthusiasm. Work sustainably.
Stanwell analyses working time recorded in Toggl to help you understand how much you work and how that time is distributed across projects, activities and working patterns.
Quick setup
Initialise Stanwell:
stanwell init
Synchronise historical data. Repeat until all missing data has been downloaded:
stanwell sync-missing
Refresh recent entries when needed:
stanwell refresh-recent
Open the interactive dashboard:
stanwell dashboard
Development
uv sync --all-groups
Format and lint the project:
uv run make tidy
Run the CI checks locally:
uv run make ci
Documentation
Build the Sphinx documentation:
uv run make docs
Open docs/_build/html/index.html to view the generated documentation.
Integration tests
Create an environment file containing an API token and workspace ID using .env.integration.example as a template.
Then run:
uv run --env-file .env.integration pytest -m integration
Licence
Stanwell is released under the MIT Licence.
1 maintainer
Metadata
1 maintainer
Release files for stanwell 0.1.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 |
|---|---|---|---|---|
| stanwell-0.1.1.tar.gz | 561.0 kB | With provenance | Details for stanwell-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| stanwell-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for stanwell-0.1.1-py3-none-any.whl |
Total release size: 630.9 kB
Release files / stanwell-0.1.1.tar.gz
| Download URL | stanwell-0.1.1.tar.gz |
|---|---|
| Size | 561.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bae58192a18daf226a737a3678ab502ef8eb73231f832e0f1aab4f994e23b1d1
|
|
BLAKE2b-256 checksum How to use checksums |
e39f13a9c9e3cf55f36f3d6dbfa1d7569dd6387438af9fe63606cbdb8b9bba99
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 4, 2026.
Transparency logRelease files / stanwell-0.1.1-py3-none-any.whl
| Download URL | stanwell-0.1.1-py3-none-any.whl |
|---|---|
| Size | 69.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f26318f31d5585a0d5ff804b61a1c5fe1fc3f20c5efc77c6a901329de38a15f0
|
|
BLAKE2b-256 checksum How to use checksums |
74fda7f1340ba32f81f0ff2648a6be9fc0459984550fc29d9d6ea63cce277dff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 4, 2026.
Transparency logSecurity for stanwell 0.1.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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for stanwell-0.1.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 Nov 4, 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.
