This release is a pre-release and may not be stable for production use.
1 maintainer
Metadata
1 maintainer
Release files for xcmp 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 | |
|---|---|---|---|---|
| xcmp-0.1a1.tar.gz | 8.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| xcmp-0.1a1-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 18.7 kB
Release files / xcmp-0.1a1.tar.gz
| Download URL | xcmp-0.1a1.tar.gz |
|---|---|
| Size | 8.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a03e90770dd73e0bf3adcf6241a4e33139d3bdfa686d97f85f3b361357a04411
|
|
BLAKE2b-256 checksum How to use checksums |
8800a4c3f90e5cd1f797431b8021ded2a515f42c5cd77474bf468585a11bb653
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.10
|
Release files / xcmp-0.1a1-py2.py3-none-any.whl
| Download URL | xcmp-0.1a1-py2.py3-none-any.whl |
|---|---|
| Size | 9.8 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
600ee45fa548d1c7f4f0204abe9852ccffb356f7ce82ed19d4ca60d6705e574e
|
|
BLAKE2b-256 checksum How to use checksums |
a4338135f2a90ed968a88d4e360f5f9ba4ee9a309cf77a09d5fb5d045ad75440
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.10
|
Security for xcmp 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.
