The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for discovers 0.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 | |
|---|---|---|---|---|
| discovers-0.1.0.tar.gz | 314 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| discovers-0.1.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 1.2 kB
Release files / discovers-0.1.0.tar.gz
| Download URL | discovers-0.1.0.tar.gz |
|---|---|
| Size | 314 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7203b2c5628328e59489191655321c66d06f2a58bf88281f2dec2e587a509d34
|
|
BLAKE2b-256 checksum How to use checksums |
26a40382992822b79eb5197f993fd9739084ac8d20b393bc0dacd7672592da14
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Release files / discovers-0.1.0-py2.py3-none-any.whl
| Download URL | discovers-0.1.0-py2.py3-none-any.whl |
|---|---|
| Size | 928 Bytes |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
542573960ec0c4ac0ece39c86b17e52dd183a5cd4479dfc9e8f69d6acd9f219b
|
|
BLAKE2b-256 checksum How to use checksums |
721811195e1aa67379ecae5e15e7d73c8c86df066a4dbc0c749a9f0a729b43fc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Security for discovers 0.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.
