hyrum
Named after Hyrum's Law: once you have enough users, every observable behaviour of your code is depended on by somebody. This tool exists to find out who that "somebody" is — by running a proposed dependency change against a fleet of consumer repositories before you ship it.
Bulk-run a check (typically lint or unit tests) across many charm repositories, optionally patching one of their dependencies first.
Install
uv tool install --prerelease=allow hyrum
Quick start
# Run tox -e unit with ops patched to a development branch:
hyrum check unit --patch 'ops @ canonical:fix/my-change' --workers 8
# Run without patching any dependency:
hyrum check unit --no-patch
# Diff the last two runs, or print one of them again:
hyrum compare ~/.cache/hyrum/results/unit.auto.prev.json \
~/.cache/hyrum/results/unit.auto.json
hyrum show ~/.cache/hyrum/results/unit.auto.json
# Reclaim the disk the runs used, keeping the checkouts:
hyrum clean
Documentation
Full documentation — including a tutorial, how-to guides, CLI reference, and background explanation — is in the docs/ directory.
1 maintainer
Metadata
1 maintainer
Release files for hyrum 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 | |
|---|---|---|---|---|
| hyrum-1.0.0.tar.gz | 275.0 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hyrum-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 382.1 kB
Release files / hyrum-1.0.0.tar.gz
| Download URL | hyrum-1.0.0.tar.gz |
|---|---|
| Size | 275.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
79c920eb79a9f540bef95c6729e89c6c91453e2c0ff0b0fa6cfe73f16cce2b99
|
|
BLAKE2b-256 checksum How to use checksums |
49d637e340e630d68af93941395fcc194e108733e024bff5beb1be57e26807e0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.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 Oct 3, 2026.
Transparency logRelease files / hyrum-1.0.0-py3-none-any.whl
| Download URL | hyrum-1.0.0-py3-none-any.whl |
|---|---|
| Size | 107.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c9271611c82baefb3576049c1acf505fb0f93d47b2dd322f129214bdcb0928b4
|
|
BLAKE2b-256 checksum How to use checksums |
dd9a17e855015aea66ff7f8b717a05c0da9b322a4318108e80715b96394dc374
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.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 Oct 3, 2026.
Transparency logSecurity for hyrum 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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for hyrum-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 Oct 3, 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.
