brumby
Analyzes fresh Python releases for worsening aspects.
Usage
uv venv .venv
. .venv/bin/activate
uv sync
scripts/poll_updates.py --include-first --interval 5 | xargs -n1 -P4 brumby assess
Library API
Use brumby.api to run the same operations as the CLI without parsing terminal
output. Each operation accepts a loaded config dict and returns a result object:
import tomllib
from brumby import api
with open("brumby.toml", "rb") as config_file:
config = tomllib.load(config_file)
result = api.check("example-package", config=config)
for difference in result.diffs:
print(difference)
Pass config=None to use built-in defaults. Unlike the CLI, the library API does
not search for a config file; callers that need non-default settings should load
and pass them explicitly.
Only the names listed in brumby.api.__all__ carry a compatibility guarantee.
Every other module and package-root convenience import is an implementation detail
and may change without notice.
Export for review
brumby export PACKAGE extracts release artifacts and writes a PROMPT.md for
an LLM to review. With two selected versions, old/ and new/ contain the extracted
artifacts for comparison. If the package has only one release, the export contains
that release in new/ and the prompt asks for a standalone inspection. A wheel is
used for that inspection when one is available. In a single-release API result,
old and old_dir are None.
Assessment results
Brumby rates change, not safety. For the usual two-release assessment, average
means the new release looks no worse than yesterday's baseline. high means it has
enough newly introduced signals to look plausibly worse than that baseline. There is
no low result: failing to find a regression does not prove that either release is
safe.
The sus and informational thresholds set how many changed findings are enough
to report high. Assessments without a usable baseline report too new rather
than treating one release as evidence of improvement. Callers must handle too new
as a third result; a conservative admission policy should treat it like high while
preserving the distinct reason.
Test
uv run pytest tests/
Version Compat
This library is compatible with Python 3.11+, but should be linted under the newest stable version.
Versioning
This library follows meanver which basically means semver along with a promise to rename when the major version changes.
License
brumby is copyright Tim Hatch, and licensed under the MIT license. See the LICENSE file for details.
Metadata
Release files for brumby 0.7.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 |
|---|---|---|---|---|
| brumby-0.7.1.tar.gz | 126.7 kB | With provenance | Details for brumby-0.7.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| brumby-0.7.1-py3-none-any.whl | Python 3 | none | any | Details for brumby-0.7.1-py3-none-any.whl |
Total release size: 175.1 kB
Release files / brumby-0.7.1.tar.gz
| Download URL | brumby-0.7.1.tar.gz |
|---|---|
| Size | 126.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0a67caecad9383d1cae019dba1ae27da7af40583a967b7cf8262ed9479d2aecb
|
|
BLAKE2b-256 checksum How to use checksums |
8c5e64fc49e0dea9a4420ab5314b5f318e1f44961d4e4dcb903a28cd14b4d5f5
|
| 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 28, 2026.
Transparency logRelease files / brumby-0.7.1-py3-none-any.whl
| Download URL | brumby-0.7.1-py3-none-any.whl |
|---|---|
| Size | 48.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4f731ee3def0486d0846f91bb95814c3e88bc188244feed1a0c9c14708a41e21
|
|
BLAKE2b-256 checksum How to use checksums |
6f1c25559558b4dd04ec9cc19787e036dbe2cca345fbbceeb4b8cf6d78018617
|
| 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 28, 2026.
Transparency logSecurity for brumby 0.7.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
Both files in this release have been uploaded with provenance metadata.
Attestation for brumby-0.7.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 Oct 28, 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.