The author of this package has not provided a project description
Metadata
Release files for siglab-py 0.11.29
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.29.tar.gz | 213.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| siglab_py-0.11.29-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 464.4 kB
Release files / siglab_py-0.11.29.tar.gz
| Download URL | siglab_py-0.11.29.tar.gz |
|---|---|
| Size | 213.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
56993621b304cb2a3d5e3aaa9fd346450c05cc256e7e5a10bdbe63acd065871a
|
|
BLAKE2b-256 checksum How to use checksums |
bf1f3215b500a576fa792d308c0ff13a83091519707cf4b185e7fc83319fe8f4
|
| 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.29-py3-none-any.whl
| Download URL | siglab_py-0.11.29-py3-none-any.whl |
|---|---|
| Size | 251.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
103f700a5e75cb24397cfed0ccdf0119e2bf6fb69706b8dbe0a5710a31b24e83
|
|
BLAKE2b-256 checksum How to use checksums |
2648a40b451ee0c44930c7b07ad05452ec436c361219d0d0d09125ce186d340c
|
| 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.29
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.