The author of this package has not provided a project description
Metadata
Release files for base-pmad-ae 0.2.0
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 | |
|---|---|---|---|---|
| base_pmad_ae-0.2.0.tar.gz | 18.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| base_pmad_ae-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 43.7 kB
Release files / base_pmad_ae-0.2.0.tar.gz
| Download URL | base_pmad_ae-0.2.0.tar.gz |
|---|---|
| Size | 18.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6d70cd265984632dd2cbcd2450c0252fba09b02ae89e92d24ddb08265e497b9c
|
|
BLAKE2b-256 checksum How to use checksums |
13a9c783580843ede7611146545c843884c73be644b1e43693427afd6e619aac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Release files / base_pmad_ae-0.2.0-py3-none-any.whl
| Download URL | base_pmad_ae-0.2.0-py3-none-any.whl |
|---|---|
| Size | 25.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f8506e8a5c5a331b12233e1eb70ab9341b08557bf1de2f5492428768cca428e3
|
|
BLAKE2b-256 checksum How to use checksums |
bb699717128ee45bdd6f8dec4c06ed72e72a5bf91c70f35faa24f8ddeb799229
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Security for base-pmad-ae 0.2.0
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.