The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for alabebm 2.2.12
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 | |
|---|---|---|---|---|
| alabebm-2.2.12.tar.gz | 60.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| alabebm-2.2.12-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 123.0 kB
Release files / alabebm-2.2.12.tar.gz
| Download URL | alabebm-2.2.12.tar.gz |
|---|---|
| Size | 60.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e6903c2605d092b35c9c640a8bfdf54bb4bb7d6b6b613234bd50b8910777d07d
|
|
BLAKE2b-256 checksum How to use checksums |
fb8d3736c2a8385fa43af2a1f7e1713b65363bad1c33d5b42e2163ff5e33f7da
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.8.19
|
Release files / alabebm-2.2.12-py3-none-any.whl
| Download URL | alabebm-2.2.12-py3-none-any.whl |
|---|---|
| Size | 62.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5cfeeaab697b9b30097c8973aaae661abfc34a1025a48e9fc50887f714789ee0
|
|
BLAKE2b-256 checksum How to use checksums |
12b5542641cd7232addf2e395eb6acfa0afdccafbc550e1a590fdeb1ba7918db
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.8.19
|
Security for alabebm 2.2.12
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.
