The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for electroanalyzer 0.1
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 | |
|---|---|---|---|---|
| electroanalyzer-0.1.tar.gz | 2.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| electroanalyzer-0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.7 kB
Release files / electroanalyzer-0.1.tar.gz
| Download URL | electroanalyzer-0.1.tar.gz |
|---|---|
| Size | 2.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d01695a3ca55318cda20de738d48b17a15704aad4161ffebd081c1695e0c6111
|
|
BLAKE2b-256 checksum How to use checksums |
6c5ee6edf8babcf13efdb495a87c5bc6b7768e9a859c36beeaabf16318de0b7b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.2
|
Release files / electroanalyzer-0.1-py3-none-any.whl
| Download URL | electroanalyzer-0.1-py3-none-any.whl |
|---|---|
| Size | 1.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c25feece4328c6df939c2d66f29f05d2f30f23725068df339f0f8de008203ffb
|
|
BLAKE2b-256 checksum How to use checksums |
e44eedb2b35fb43eae53aacae0dd2f03198dcd76ed081961aba91cd5169d5994
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.2
|
Security for electroanalyzer 0.1
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.
