The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for walkerlab 0.0.0
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 | |
|---|---|---|---|---|
| walkerlab-0.0.0.tar.gz | 718 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| walkerlab-0.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.7 kB
Release files / walkerlab-0.0.0.tar.gz
| Download URL | walkerlab-0.0.0.tar.gz |
|---|---|
| Size | 718 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
445807a7eef665701f37ac666a6605dab52eb801130dab9caab7c6c1a6f19175
|
|
BLAKE2b-256 checksum How to use checksums |
4eb9315d143042c033360b01c9dd3dd3ca41091aa9ab8ad1d79a6baa407011b2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Release files / walkerlab-0.0.0-py3-none-any.whl
| Download URL | walkerlab-0.0.0-py3-none-any.whl |
|---|---|
| Size | 966 Bytes |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
49f6136da0c423bf3597ebef8d11399392b0289a1eab6ec52aa9a23df21fd10e
|
|
BLAKE2b-256 checksum How to use checksums |
c174b1f5ccd00ad5b2441aff3aad36cf5f086733eb4e95009f5dfb83c7215859
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Security for walkerlab 0.0.0
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.
