Skip to main content

Noisy Secrets

A Noisy Secret is a bearer credential that is easy to detect when leaked. It contains checksums, so it can be validated offline, and an optional namespace identifying the issuer.

import noisysecrets

secret = noisysecrets.create(b"example.org")
noisysecrets.verify(secret)  # True

verify checks only the format and the checksums. It does not tell you that a secret was issued by you, and must not be used on its own to authenticate anyone.

This package implements the draft Noisy Secrets specification. It is licensed under the Apache License 2.0.

Reporting issues

Report bugs at https://github.com/apache/tooling-noisy-secrets/issues.

Do NOT report security vulnerabilities through public GitHub issues. Please report security vulnerabilities to the Apache Security Team by emailing security@apache.org. This is a private mailing list. Please send one plain-text, unencrypted, email for each vulnerability you are reporting. For complete details on reporting and the process, see the ASF Security Team page.

Versions

Releases are numbered 0.0.N, starting at 0.0.1. Between releases, the version on main is that of the next release with .dev0+dev appended, such as 0.0.1.dev0+dev before the first release. The +dev makes it a local version, which PyPI will not accept, so a build from source can never be published as a release. The .dev0 makes it a pre-release, so installers that can see both choose the release.

To release, run sh scripts/phase.sh release on an up to date main. It changes the version from 0.0.N.dev0+dev to 0.0.N, commits, tags that commit v0.0.N, and pushes the commit and the tag together. The upload waits until two members of ASF Tooling approve it at https://releases.apache.org/gates. Afterwards, run sh scripts/phase.sh develop to change the version to 0.0.(N+1).dev0+dev, commit, and push.

Run uv run prek install once after cloning. Its hooks check these rules on every commit and push, along with the linters and tests, and CI checks them again on every push to main and every pull request.

Metadata

Release files for noisysecrets 0.0.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for noisysecrets 0.0.1
File Size Uploaded Provenance Actions
noisysecrets-0.0.1.tar.gz 9.1 kB With provenance Details for noisysecrets-0.0.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for noisysecrets 0.0.1
File Interpreter ABI Platform Actions
noisysecrets-0.0.1-py3-none-any.whl Python 3 none any Details for noisysecrets-0.0.1-py3-none-any.whl

Total release size: 19.2 kB

Release files / noisysecrets-0.0.1.tar.gz

Download URL noisysecrets-0.0.1.tar.gz
Size 9.1 kB
Tags Source
SHA-256 checksum
How to use checksums
1a5cdf3b8e7fba8b8f65bd2fb7115b1daf482b5f9b41e344cee6261c1dfa89fc
BLAKE2b-256 checksum
How to use checksums
eab5fa736ba7e09ff4bde79f2b32f72af361aa39909400a1fc19062947bf85b9
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 Nov 17, 2026.

Transparency log

Release files / noisysecrets-0.0.1-py3-none-any.whl

Download URL noisysecrets-0.0.1-py3-none-any.whl
Size 10.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
9c5c869b3bb1cc334519f2afc4506df691b44465d11cb36d4472aff26347fe4f
BLAKE2b-256 checksum
How to use checksums
50d3f72f127c890a479ddd611095262bce16819360f902b83c63df047d973392
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 Nov 17, 2026.

Transparency log

Security for noisysecrets 0.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.

Select from 2 files

Attestation for noisysecrets-0.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 Nov 17, 2026.

Transparency log

A 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.

Release history Release notifications | RSS feed

This release

0.0.1 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page