The author of this package has not provided a project description
Metadata
Release files for siglab-py 0.11.27
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.27.tar.gz | 213.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| siglab_py-0.11.27-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 464.3 kB
Release files / siglab_py-0.11.27.tar.gz
| Download URL | siglab_py-0.11.27.tar.gz |
|---|---|
| Size | 213.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
259c97ae449929572564b6faa89bd6287d594e9dd482b845da2d69ac1cae1234
|
|
BLAKE2b-256 checksum How to use checksums |
a9289ac385d6fb8734a479386e8852ccce33d92186d74186069084e15cac8efe
|
| 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.27-py3-none-any.whl
| Download URL | siglab_py-0.11.27-py3-none-any.whl |
|---|---|
| Size | 251.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
45b6414a9c71894cc6e17b24db807ddcf9a44c1273ca3b4e4f294fe1ab518b04
|
|
BLAKE2b-256 checksum How to use checksums |
27c2262f499084039d72039d5521a357d08f2fb20b367144a08a627091025a84
|
| 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.27
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.