depesha
The command-line client for Depesha, transactional email for every project you run, with the /depesha Claude skill built in.
uv tool install depesha # or: pipx install depesha
depesha skill install # the skill, into ~/.claude/skills/depesha
depesha login --token-file key.txt # a dp_live_, dp_test_ or dp_op_ key
depesha templates push templates/
depesha send sign-in-code --to you@example.com --var code=428913 --var-json expires_minutes=10
depesha <noun> <verb> maps to GraphQL against https://api.depesha.com/graphql; depesha gql and depesha schema --sdl reach the whole API. Output is JSON; exit codes are 0 ok, 1 API error (with extensions.code), 2 transport, 3 usage or configuration. Credentials live in ~/.depesha/credentials.json (mode 600); DEPESHA_TOKEN, DEPESHA_URL, DEPESHA_PROFILE and DEPESHA_PROJECT override them.
The core uses only the standard library. depesha admin (operator only, on the owner's machine) needs depesha[admin].
Full reference: depesha skill show references/cli.md.
1 maintainer
Metadata
1 maintainer
Release files for depesha 0.2.0
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 |
|---|---|---|---|---|
| depesha-0.2.0.tar.gz | 67.0 kB | With provenance | Details for depesha-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| depesha-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for depesha-0.2.0-py3-none-any.whl |
Total release size: 134.7 kB
Release files / depesha-0.2.0.tar.gz
| Download URL | depesha-0.2.0.tar.gz |
|---|---|
| Size | 67.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cadee072a2994b7c5d75ab6b96ea4456e0e8d02952ba162060837a5335f29164
|
|
BLAKE2b-256 checksum How to use checksums |
05385ab216aebe043bc680648a1105cad445d5621fa7965c5bacd76f0d91b7b1
|
| 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 Oct 29, 2026.
Transparency logRelease files / depesha-0.2.0-py3-none-any.whl
| Download URL | depesha-0.2.0-py3-none-any.whl |
|---|---|
| Size | 67.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1f12ce9ecc1cffa9f4d0966a202eced1d0bbab809ac5e40b8d04007bc98c4b17
|
|
BLAKE2b-256 checksum How to use checksums |
cd50368992c220d08c6f6b39f75588ff405b6badb3b5ef353ff51fc5d421ca6e
|
| 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 Oct 29, 2026.
Transparency logSecurity for depesha 0.2.0
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 depesha-0.2.0.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 Oct 29, 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.
