The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for xpl-intel 1.2.0
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 | |
|---|---|---|---|---|
| xpl_intel-1.2.0.tar.gz | 25.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| xpl_intel-1.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 46.3 kB
Release files / xpl_intel-1.2.0.tar.gz
| Download URL | xpl_intel-1.2.0.tar.gz |
|---|---|
| Size | 25.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b7a7f1846d808c370989d48641be41b7e1767d36910ff10bb6c056dbb6389ddf
|
|
BLAKE2b-256 checksum How to use checksums |
c755310a0d9792b0e173cc3078fbab26a8ffc3f3687a9fccff2b7e99fc3c5e08
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.4
|
Release files / xpl_intel-1.2.0-py3-none-any.whl
| Download URL | xpl_intel-1.2.0-py3-none-any.whl |
|---|---|
| Size | 20.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0bf322ecf7e3305c2cb3c74a09d100cef4b1ca672567967e79acb9d0056ceb24
|
|
BLAKE2b-256 checksum How to use checksums |
48f150e27d5757a8e7942fb5cf499ecd9d713c0869f43f39c1304962d13f7dca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.4
|
Security for xpl-intel 1.2.0
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.
