See the README on GitHub.
Metadata
Release files for UW-RestClients-Mailman 2.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 | |
|---|---|---|---|---|
| uw_restclients_mailman-2.1.tar.gz | 10.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| uw_restclients_mailman-2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.9 kB
Release files / uw_restclients_mailman-2.1.tar.gz
| Download URL | uw_restclients_mailman-2.1.tar.gz |
|---|---|
| Size | 10.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3275d3215712b8cb77cbb480369005d50db8b240e6888da6135f229191ba638a
|
|
BLAKE2b-256 checksum How to use checksums |
9e63a997aec651d808bb11a03cb7a98e5aa6b899f190af515149071ada704745
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.11
|
Release files / uw_restclients_mailman-2.1-py3-none-any.whl
| Download URL | uw_restclients_mailman-2.1-py3-none-any.whl |
|---|---|
| Size | 19.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
63df00986cc1861ed1e0547b80d2e17f3e7827384e615b3f9e3e94ec0a179366
|
|
BLAKE2b-256 checksum How to use checksums |
42627d9d2fd22a899d8096dbffae46907d705aa6803fcef835f07570b797e73c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.11
|
Security for UW-RestClients-Mailman 2.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.
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.