Blot
A pre-commit check that has read your project's history.
Blot warns you before you commit when your change:
- removes a fix: deletes or edits code that was added to fix a bug
- re-adds a bug: brings back a line that a bug fix deliberately removed
- forgets a related file: changes
Abut notB, when the two almost always change together
It runs locally, needs no account or AI, and stays quiet unless the history gives it a real reason to speak.
pip install blot-git
cd your-repo
blot index # optional: the first check indexes history itself
blot install-hook # adds Blot to your pre-commit hook
blot why src/app.py:42 # which commit explains this line, skipping refactors
blot index --github # optional: issue/PR titles and labels via the gh CLI
Status: pre-alpha. All three checks work. Replayed on 500 recent commits each of Flask, requests, Express, Django and React, Blot warns on 0.6–10% of commits; see the bench results on GitHub. Please report false alarms.
Meet Sora the slime, read the docs, or contribute on GitHub: https://github.com/Sym-jay/Blot
1 maintainer
Metadata
1 maintainer
Release files for blot-git 0.3.2
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 | |
|---|---|---|---|---|
| blot_git-0.3.2.tar.gz | 364.9 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| blot_git-0.3.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 402.5 kB
Release files / blot_git-0.3.2.tar.gz
| Download URL | blot_git-0.3.2.tar.gz |
|---|---|
| Size | 364.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d666b1e5be9396bc6e34e0ce0f8523273b1748ae3bc675cd7ab4527c9e5e11b4
|
|
BLAKE2b-256 checksum How to use checksums |
3d22943fac594076d02b575ee697909bb8a8e5d2fe564c063bf652241b6cdfc4
|
| 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 25, 2026.
Transparency logRelease files / blot_git-0.3.2-py3-none-any.whl
| Download URL | blot_git-0.3.2-py3-none-any.whl |
|---|---|
| Size | 37.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bb15c931dc7a9d049aba255a6d28b3352839e9e2ca67ae890cb7e64470428486
|
|
BLAKE2b-256 checksum How to use checksums |
27cbad0714e9333842ac29eb0798a40a9dcad0e79c9be65c091de2c403f2702a
|
| 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 25, 2026.
Transparency logSecurity for blot-git 0.3.2
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 blot_git-0.3.2.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 25, 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.
