securelogging
Remove secrets from logging
This project enables redaction in logs based on a global set of secrets. These secrets are managed by add_secret and remove_secret.
In this example, we have a key that we want to have a key redacted from the log. To accomplish this, we need to define the key and add it to secret. When we generate our logger, we do it within UseLoggingRedactor. When the message is logged, it will appear as beanbean - Assigned key: JH***QE
Since the log record is modified, propagation still occurs as expected, but will do so with the redacted message. The output of this will be
beanbean - Assigned key: JH***QE
bean - Assigned key: JH***QEYou can also redact a single message. This could be useful if you normally do not want something redacted, but in specific use-cases you need it to be redacted. The output of this will be
Assigned non-redacted key: JHKLASDJKQWEBBNMASDHJK:LGHJKWQE
Assigned non-redacted key: JH***QENote
This project has been set up using PyScaffold 4.6. For details and usage information on PyScaffold see https://pyscaffold.org/.
1 maintainer
Metadata
1 maintainer
Release files for securelogging 1.0.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 |
|---|---|---|---|---|
| securelogging-1.0.1.tar.gz | 17.9 kB | With provenance | Details for securelogging-1.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| securelogging-1.0.1-py3-none-any.whl | Python 3 | none | any | Details for securelogging-1.0.1-py3-none-any.whl |
Total release size: 22.9 kB
Release files / securelogging-1.0.1.tar.gz
| Download URL | securelogging-1.0.1.tar.gz |
|---|---|
| Size | 17.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9ddd7f9d387536e2a19648c8e68de973b95bfef828e3c0a824c510710313fdc7
|
|
BLAKE2b-256 checksum How to use checksums |
4d9e6c68009da6a3021a3629e91056198cebd44f3ee57a57a16e2f78999a6e7b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 May 16, 2025.
Transparency logRelease files / securelogging-1.0.1-py3-none-any.whl
| Download URL | securelogging-1.0.1-py3-none-any.whl |
|---|---|
| Size | 5.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d1445f92a5555d94702eec07ff253ee17bd63aba5bdd3e6af1ec3f7b29e1a50c
|
|
BLAKE2b-256 checksum How to use checksums |
b535ccc85faccc16b81523b1e170ab2a703e7b1333b4a9805f546c5c79414326
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 May 16, 2025.
Transparency logSecurity for securelogging 1.0.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 securelogging-1.0.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 May 16, 2025.
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.
