The author of this package has not provided a project description
Metadata
Release files for compound-reading 0.0.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 | |
|---|---|---|---|---|
| compound_reading-0.0.1.tar.gz | 478 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| compound_reading-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.6 kB
Release files / compound_reading-0.0.1.tar.gz
| Download URL | compound_reading-0.0.1.tar.gz |
|---|---|
| Size | 478 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7c0f3db43c61b67e341f636a03aeafafff4766e3234f66bfbc260414477d9129
|
|
BLAKE2b-256 checksum How to use checksums |
4d0dd7fe8d02181e5a0e8334a46ed14e6a9569b5abf5adbe4055c21432a2a7b9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.2
|
Release files / compound_reading-0.0.1-py3-none-any.whl
| Download URL | compound_reading-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8e7ac3e1342b6e45860c4d04453f5317afdd999a721f0e67720a76a190c833d5
|
|
BLAKE2b-256 checksum How to use checksums |
64e821ea050fade08e7094919974d198c95582888f128979c17944cf5cc71d18
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.2
|
Security for compound-reading 0.0.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.