The author of this package has not provided a project description
Metadata
Release files for siglab-py 0.11.25
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.25.tar.gz | 212.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| siglab_py-0.11.25-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 463.3 kB
Release files / siglab_py-0.11.25.tar.gz
| Download URL | siglab_py-0.11.25.tar.gz |
|---|---|
| Size | 212.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9e11f2a2db99935a1b2ca80bce95c36414d4141cf0168588d28d822af8226849
|
|
BLAKE2b-256 checksum How to use checksums |
884e2f47614295ca4f9008aa003f074e0697d916af847f8ae1f58b5f8c9994c2
|
| 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.25-py3-none-any.whl
| Download URL | siglab_py-0.11.25-py3-none-any.whl |
|---|---|
| Size | 250.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4f62b49dabb115380b4efc1373bad696a7b600d2772329990539faa6a2acc80a
|
|
BLAKE2b-256 checksum How to use checksums |
f511409914a0351ca1747586fdff5d126f8c853ff25f24021f76d3860a6d03ce
|
| 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.25
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.