The author of this package has not provided a project description
Metadata
Release files for siglab-py 0.11.28
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.28.tar.gz | 213.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| siglab_py-0.11.28-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 464.3 kB
Release files / siglab_py-0.11.28.tar.gz
| Download URL | siglab_py-0.11.28.tar.gz |
|---|---|
| Size | 213.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
731503aa0c9f75865eb9a263089e1c2adc6adbd8b9cb981afe53dc46a368d7b8
|
|
BLAKE2b-256 checksum How to use checksums |
0b370104b477f67aa3c1ddcc60aead0922d27c89cedfd040479c99297f91b4e7
|
| 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.28-py3-none-any.whl
| Download URL | siglab_py-0.11.28-py3-none-any.whl |
|---|---|
| Size | 251.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
89f7b1c7d6ad29d9c20bc961dbb9461fa7b6223ec534b0fe6de02ed2846e0b29
|
|
BLAKE2b-256 checksum How to use checksums |
6e6d5f62edbd51c1439982f1b76fdf0ebe472df81240ef3b3dc7b42e6f228a0e
|
| 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.28
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.