This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Consider using release 0.1.0a13 instead.
Reason given by maintainers: A rate-limited upstream source could pass unchecked, and a non-UTF-8 file name could end a scan; use 0.1.0a9 or later.
limbowatch
The library behind Limbowatch: it tracks security advisories in limbo, meaning published by maintainers on GitHub but not yet in GitHub's reviewed Advisory Database or OSV, so scanners that read those databases don't report them.
Most people want the command line instead: pip install limbowatch-cli. See the watcher guide.
Advisory data: GitHub repository security advisories and the GitHub Advisory Database (CC BY 4.0), via the limbo feed (CC BY 4.0). Code: Apache-2.0.
1 maintainer
Metadata
1 maintainer
Release files for limbowatch 0.1.0a8
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 |
|---|---|---|---|---|
| limbowatch-0.1.0a8.tar.gz | 179.1 kB | With provenance | Details for limbowatch-0.1.0a8.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| limbowatch-0.1.0a8-py3-none-any.whl | Python 3 | none | any | Details for limbowatch-0.1.0a8-py3-none-any.whl |
Total release size: 385.8 kB
Release files / limbowatch-0.1.0a8.tar.gz
| Download URL | limbowatch-0.1.0a8.tar.gz |
|---|---|
| Size | 179.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b49fceab68fc6e62b8072038b7e8e20779e1b9a30db712236c539ea67678a5c5
|
|
BLAKE2b-256 checksum How to use checksums |
20e34fbc20524a50b87e28c98ca7709d3ae51a32cad5799935f2cd7adcbfbaad
|
| 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 11, 2026.
Transparency logRelease files / limbowatch-0.1.0a8-py3-none-any.whl
| Download URL | limbowatch-0.1.0a8-py3-none-any.whl |
|---|---|
| Size | 206.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c25c4a3c41bff1f1722009b9eda3decc3dd4e335d2a0beed501b7241d482916f
|
|
BLAKE2b-256 checksum How to use checksums |
aa6929656f6ca90126490a01d18047911f564f38857c7cd06e1e3f266486bea8
|
| 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 11, 2026.
Transparency logSecurity for limbowatch 0.1.0a8
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 limbowatch-0.1.0a8.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 11, 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.
