The author of this package has not provided a project description
Metadata
Release files for siglab-py 0.11.26
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 | |
|---|---|---|---|---|
| siglab_py-0.11.26.tar.gz | 212.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| siglab_py-0.11.26-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 463.4 kB
Release files / siglab_py-0.11.26.tar.gz
| Download URL | siglab_py-0.11.26.tar.gz |
|---|---|
| Size | 212.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
34d980c23959cd8f52cd586fa19b3dcb19d82ab253e8150969696f42a3bf468c
|
|
BLAKE2b-256 checksum How to use checksums |
311f259f96bdbd1b5a0dc4b6056dbf7da28db846e3fe5381b30dbc7ea73b22fc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.14
|
Release files / siglab_py-0.11.26-py3-none-any.whl
| Download URL | siglab_py-0.11.26-py3-none-any.whl |
|---|---|
| Size | 250.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1c4cf115f5351792fdab2d3b1c1744c9d632422ef3b054716ba3c3bfc89f4289
|
|
BLAKE2b-256 checksum How to use checksums |
a5736bd7b7256d34004e3a3c2b1ed7fca356971c16ee035730327c3b977c7a78
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.14
|
Security for siglab-py 0.11.26
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.