The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for electroreception 0.1.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 | |
|---|---|---|---|---|
| electroreception-0.1.0.tar.gz | 496 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| electroreception-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.6 kB
Release files / electroreception-0.1.0.tar.gz
| Download URL | electroreception-0.1.0.tar.gz |
|---|---|
| Size | 496 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2611094c46df65d5bd85e4a82619f64b307fdeabe31965886963d6625dae9244
|
|
BLAKE2b-256 checksum How to use checksums |
2b8375c91fd70c4e5c38c1c99ffb3375fa4a183234fde306a3e069b60351a99d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.2
|
Release files / electroreception-0.1.0-py3-none-any.whl
| Download URL | electroreception-0.1.0-py3-none-any.whl |
|---|---|
| Size | 1.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9cc546170e7a7ff9cba150b6810de305d0b902d81248202d8efdac78a7bb89cf
|
|
BLAKE2b-256 checksum How to use checksums |
acb12fd16c20a17ef4371a2eabc3f46741793b610e8749dfb37dfc72209b72e4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.2
|
Security for electroreception 0.1.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.
