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