The author of this package has not provided a project description
Metadata
Release files for xfc-client 1.1.2
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 | |
|---|---|---|---|---|
| xfc_client-1.1.2.tar.gz | 6.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| xfc_client-1.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.1 kB
Release files / xfc_client-1.1.2.tar.gz
| Download URL | xfc_client-1.1.2.tar.gz |
|---|---|
| Size | 6.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2ab6af2b388e8faad383da003276bccd2cbf0a1bbf4864cadd9d7bac4398852d
|
|
BLAKE2b-256 checksum How to use checksums |
3ae9ec6502a819cd0bbb1c5a06323c39407ff3ff7159a0471ed8718eac4b02f7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.6
|
Release files / xfc_client-1.1.2-py3-none-any.whl
| Download URL | xfc_client-1.1.2-py3-none-any.whl |
|---|---|
| Size | 6.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6f26224ab6175dc95704c02739c309778367bd8321fc024116d8dee870d0c04e
|
|
BLAKE2b-256 checksum How to use checksums |
37a533904842f47ee522de09be5e4efcf700d43995ae3385aedfea8ae4868fca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.6
|
Security for xfc-client 1.1.2
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.
