tenhaw-delivery-metrics
DORA and flow metrics for engineers building internal delivery dashboards.
When to use
- Use for deterministic metrics from supplied deployment, incident, commit and work-item events.
- Use for local GitHub and Jira Cloud collection with the user's own environment credentials.
- Do not use merge proxies as evidence of real production deployments or to rank individuals.
Install
pip install tenhaw-delivery-metrics
Quick start
from tenhaw_delivery_metrics import compute_metrics
report = compute_metrics([], {"since": "2026-01-01T00:00:00Z", "until": "2026-02-01T00:00:00Z"})
assert report["metrics"]["changeFailRate"]["value"] is None
API
compute_metrics(events, config), score_delivery_health(report), collect_github(repos, since, until=None, cache=True) and collect_jira(jql, since, status_to_stage=...).
Collectors run locally. Set GITHUB_TOKEN, or JIRA_BASE_URL, JIRA_EMAIL and JIRA_API_TOKEN.
GitHub tokens need read-only metadata, contents, deployments, pull requests and issues access.
Jira status names must be mapped to todo, active, waiting or done. GitHub incident issues
need tenhaw-deployment: <id>, tenhaw-started: <ISO timestamp> and optional
tenhaw-restored: <ISO timestamp> markers. Closing an issue does not prove service restoration.
A failed deployment job does not prove a production change failure: failure/error statuses
are excluded unless the deployment payload explicitly sets tenhaw.changeFailure: true.
Successes and explicitly linked production incidents support change-failure measurement;
collectors cannot prove that the supplied incident dataset is complete. Collector caches
contain normalised events, never raw API responses or tokens. Use cache=False to disable them.
Methodology and sources
DORA's current five metrics are reported with
sample sizes, explicit deployment/incident linkage and caveats. Missing evidence returns null
where appropriate. Merges used as deployment proxies are flagged. No composite health grade or
unsourced performance bands are generated. Periods are half-open UTC intervals [since, until).
Built by Tenhaw
Tenhaw builds practical AI and delivery tools. For help applying the findings, book a discovery call.
Metadata
Release files for tenhaw-delivery-metrics 1.0.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 |
|---|---|---|---|---|
| tenhaw_delivery_metrics-1.0.0.tar.gz | 13.3 kB | With provenance | Details for tenhaw_delivery_metrics-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tenhaw_delivery_metrics-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for tenhaw_delivery_metrics-1.0.0-py3-none-any.whl |
Total release size: 28.4 kB
Release files / tenhaw_delivery_metrics-1.0.0.tar.gz
| Download URL | tenhaw_delivery_metrics-1.0.0.tar.gz |
|---|---|
| Size | 13.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f6976697559aeeb3656c23545001a177c35ab1dcf6a99510d12f3c931800da70
|
|
BLAKE2b-256 checksum How to use checksums |
445eac930b1402825eb07a74fbe795310cc583e95eeba73ffd262e3f4fa4b6b0
|
| 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 16, 2026.
Transparency logRelease files / tenhaw_delivery_metrics-1.0.0-py3-none-any.whl
| Download URL | tenhaw_delivery_metrics-1.0.0-py3-none-any.whl |
|---|---|
| Size | 15.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
90a2e21cc2cd9a4223f95e52a945592679b7474117fa4da0b04e300a652b8ed8
|
|
BLAKE2b-256 checksum How to use checksums |
ffef36ee2d45d5dfa856eb6aacfe3dcf73b05f6088883a888687012ffc71d47a
|
| 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 16, 2026.
Transparency logSecurity for tenhaw-delivery-metrics 1.0.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 tenhaw_delivery_metrics-1.0.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 Nov 16, 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.