This release is a pre-release and may not be stable for production use.
1 maintainer
Metadata
1 maintainer
Release files for patroller 0.1a1
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 | |
|---|---|---|---|---|
| patroller-0.1a1.tar.gz | 1.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| patroller-0.1a1-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 3.9 kB
Release files / patroller-0.1a1.tar.gz
| Download URL | patroller-0.1a1.tar.gz |
|---|---|
| Size | 1.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4d25d3f5e759d9ca8b006cbf70467391434326c7725230f40629c8346711c74f
|
|
BLAKE2b-256 checksum How to use checksums |
e3db4dc881146b269a666c27ee6dcc5c4ff68865f23043636ffb48f51f4a1c1f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.23
|
Release files / patroller-0.1a1-py2.py3-none-any.whl
| Download URL | patroller-0.1a1-py2.py3-none-any.whl |
|---|---|
| Size | 2.0 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
37ee47fc5539b04fd46942d279acf334d9d5e1b49db7e488e33b1c5240cb67b8
|
|
BLAKE2b-256 checksum How to use checksums |
c3730a421e0c63344e048da3110d79fe7e617f75917ba41147d35fc44221c3e3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.23
|
Security for patroller 0.1a1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
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.
