1 maintainer
Metadata
1 maintainer
Release files for splitscreen 0.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 | |
|---|---|---|---|---|
| splitscreen-0.1.2.tar.gz | 2.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| splitscreen-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.0 kB
Release files / splitscreen-0.1.2.tar.gz
| Download URL | splitscreen-0.1.2.tar.gz |
|---|---|
| Size | 2.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
58f7b83a6b2e47d21da123864fff9263dcad18e7d08604e9abd375280967727a
|
|
BLAKE2b-256 checksum How to use checksums |
dc42374ce2c89fb835ac3dce65489a83138f8328f5cf46abf95c99e51cbe3f11
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.7.0 CPython/3.11.4 Linux/6.5.11-300.fc39.x86_64
|
Release files / splitscreen-0.1.2-py3-none-any.whl
| Download URL | splitscreen-0.1.2-py3-none-any.whl |
|---|---|
| Size | 2.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fa15fb2fa0c90b9affc9061fb9f8e9111f3dc7b566fd444694f87d299de8c6eb
|
|
BLAKE2b-256 checksum How to use checksums |
6aa4c00589e95c3f456f32f90ff8f66449a022942268bb3d5615da97a32f689e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.7.0 CPython/3.11.4 Linux/6.5.11-300.fc39.x86_64
|
Security for splitscreen 0.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.
