omerta
Fail when a value of your env files, e.g. an API key in .env, is in git: in the staged changes, in a tracked file, or anywhere in the history.
uvx omerta check --all # every tracked file
uvx omerta history # every commit, tag and message
- Matches your actual values, as written and as encoded in URLs, JSON and base64, so it catches secrets of any format; it complements pattern scanners, which find what looks like a key.
- Reports the file, the line and the variable's name, never the value; a tracked env file is a leak in itself.
- Runs entirely offline.
As a pre-commit hook:
repos:
- repo: https://github.com/shcherbak-ai/omerta
rev: v0.1.0
hooks:
- id: omerta
With Husky, Lefthook or a plain git hook: uvx omerta@0.1.0 check.
See the repository for the options, CI and configuration.
Licensed under MIT.
1 maintainer
Metadata
1 maintainer
Release files for omerta 0.1.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 | |
|---|---|---|---|---|
| omerta-0.1.0.tar.gz | 24.1 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| omerta-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 51.4 kB
Release files / omerta-0.1.0.tar.gz
| Download URL | omerta-0.1.0.tar.gz |
|---|---|
| Size | 24.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
da1758e5a7d8c961862207d72e187c0d5870956d36254cd5f578b0f1ad1d8551
|
|
BLAKE2b-256 checksum How to use checksums |
bb80aea93b501a771d6c3c387bee4d3e78a5cbd8c5c4c094209d377cd07f93c2
|
| 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 / omerta-0.1.0-py3-none-any.whl
| Download URL | omerta-0.1.0-py3-none-any.whl |
|---|---|
| Size | 27.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
00d670e657fc0a693af65ee8d9ec1ee7c8ff176661edab0ab85958e48f7f4595
|
|
BLAKE2b-256 checksum How to use checksums |
90b86921c71aefc2625c21edc7552d619fdba7d001be4fa4b0f8cbc58c61cd96
|
| 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 omerta 0.1.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 omerta-0.1.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 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.
