The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for pygopherd 3.1.0
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 | |
|---|---|---|---|---|
| pygopherd-3.1.0.tar.gz | 48.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pygopherd-3.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 106.9 kB
Release files / pygopherd-3.1.0.tar.gz
| Download URL | pygopherd-3.1.0.tar.gz |
|---|---|
| Size | 48.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ebea9464907d103123ef02baa43c989025e459e42ebd54df6110f2ea863ffd28
|
|
BLAKE2b-256 checksum How to use checksums |
f57e93bf5d09958b54eaf32918bb6e41b671a1b0eb6da55fda777d48ab4d2a10
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.5
|
Release files / pygopherd-3.1.0-py3-none-any.whl
| Download URL | pygopherd-3.1.0-py3-none-any.whl |
|---|---|
| Size | 58.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f4d40c66155c1a93d44d2c70deb93bcc8129e22b9fdfe25c8b3a08b72862b6b3
|
|
BLAKE2b-256 checksum How to use checksums |
f78fe6705c6925e4b601ff6fd3dbcea827b0beba7246603591b86bc47e36d9e2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.5
|
Security for pygopherd 3.1.0
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.
