The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for bayse-summary 1.0.3
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 | |
|---|---|---|---|---|
| bayse-summary-1.0.3.tar.gz | 2.6 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bayse_summary-1.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.5 MB
Release files / bayse-summary-1.0.3.tar.gz
| Download URL | bayse-summary-1.0.3.tar.gz |
|---|---|
| Size | 2.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8d08010e7e386da49e7d71b3f6f8b40b02a48d8a8aaf060347f4b3de22491a7d
|
|
BLAKE2b-256 checksum How to use checksums |
b262cc6bca8c517192c6d1d00595d13081b9f5b000b94f933da1db7f7c9739bc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.6
|
Release files / bayse_summary-1.0.3-py3-none-any.whl
| Download URL | bayse_summary-1.0.3-py3-none-any.whl |
|---|---|
| Size | 2.9 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
70dc16b8c09b05f7bdd216b5955be328c6d46bd96d228cae76748d0b5e2fa50c
|
|
BLAKE2b-256 checksum How to use checksums |
06a0e1d1688e1b91f92a4193fddbf947fecf1397a2bcd1fd8cc095348a4a42cf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.6
|
Security for bayse-summary 1.0.3
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.
