The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for xpl-intel 2.0.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-2.0.0.tar.gz | 25.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| xpl_intel-2.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 46.5 kB
Release files / xpl_intel-2.0.0.tar.gz
| Download URL | xpl_intel-2.0.0.tar.gz |
|---|---|
| Size | 25.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e602910815f2e0c4f7839134d6706af6ad0d99604f9a8b30d41e8cabe24cebe6
|
|
BLAKE2b-256 checksum How to use checksums |
e13bff66a3e0cfefc4cd5fc846ff580a2efeaaabb57b5e644f5b8c66790e9ae0
|
| 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-2.0.0-py3-none-any.whl
| Download URL | xpl_intel-2.0.0-py3-none-any.whl |
|---|---|
| Size | 20.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4c49d11d7cf202e43d7aaac1c29e769df58aaf601a3f00199fda4d9ed6eed05a
|
|
BLAKE2b-256 checksum How to use checksums |
7e1451ba536eff5a49420071996f7bb28011beceeb6f86714b2d5206fe79b9ee
|
| 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 2.0.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.
