1 maintainer
Metadata
1 maintainer
Release files for xcj 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 | |
|---|---|---|---|---|
| xcj-0.0.1.tar.gz | 3.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| xcj-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.9 kB
Release files / xcj-0.0.1.tar.gz
| Download URL | xcj-0.0.1.tar.gz |
|---|---|
| Size | 3.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bf45941c049d9e482c7d2e1bb9a79d84fcc1e4125be2127f36d257bb94bea203
|
|
BLAKE2b-256 checksum How to use checksums |
7b39c09f96d94be94b34a9eea3859e939ef251239fd6c2b58b6c87e286734150
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.15.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.2.0 requests-toolbelt/0.8.0 tqdm/4.32.2 CPython/3.5.2
|
Release files / xcj-0.0.1-py3-none-any.whl
| Download URL | xcj-0.0.1-py3-none-any.whl |
|---|---|
| Size | 7.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4a6e44fb05c4fb160811f0db8ae970ec68db783936bed55b18d1f912927a40a3
|
|
BLAKE2b-256 checksum How to use checksums |
c5c926d222e22717242361fee83c098da179145a292fdfed48938a66dfabc7a0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.15.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.2.0 requests-toolbelt/0.8.0 tqdm/4.32.2 CPython/3.5.2
|
Security for xcj 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.
