The author of this package has not provided a project description
Metadata
Release files for artex-client 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 | |
|---|---|---|---|---|
| artex_client-0.0.1.tar.gz | 3.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| artex_client-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.2 kB
Release files / artex_client-0.0.1.tar.gz
| Download URL | artex_client-0.0.1.tar.gz |
|---|---|
| Size | 3.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6be2fb3d3319b60fc70233425cebb5efea5520b7d7c8591990b324e8270f65d0
|
|
BLAKE2b-256 checksum How to use checksums |
309bdd0ed4bd8f94a535dd5050c95d2cd68d8f91542178fd0c992f83c419ec64
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Release files / artex_client-0.0.1-py3-none-any.whl
| Download URL | artex_client-0.0.1-py3-none-any.whl |
|---|---|
| Size | 4.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cb7b62876d11d6b1f33d88688bcf39698e809ff8b6970cd5957261d1e67fc931
|
|
BLAKE2b-256 checksum How to use checksums |
8adcca14bbad9c982bda05e84821f90e419f30e7427b7aff940e9c043b40ec8d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Security for artex-client 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.