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