Metadata
Release files for split-l2t 0.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 | |
|---|---|---|---|---|
| split_l2t-0.0.0.tar.gz | 734 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| split_l2t-0.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.1 kB
Release files / split_l2t-0.0.0.tar.gz
| Download URL | split_l2t-0.0.0.tar.gz |
|---|---|
| Size | 734 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8c222fb6c63aba00c4dc927085d69b8a738ea3cc0db91dd23fd2c849d4aaca90
|
|
BLAKE2b-256 checksum How to use checksums |
75cfa90bcac5f1dc67755221cbe27b2368a6f2a63a8b8e1d89a775559f253b01
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Release files / split_l2t-0.0.0-py3-none-any.whl
| Download URL | split_l2t-0.0.0-py3-none-any.whl |
|---|---|
| Size | 1.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0221722703b35cf201ea2a4239cd975fa7f2926e730f8464578461de795ed656
|
|
BLAKE2b-256 checksum How to use checksums |
8f10ec4bff3cea660523a8a4cb3349c1d47c0de0ba8564c4f80aaa066b69109d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Security for split-l2t 0.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.