The author of this package has not provided a project description
Metadata
Release files for base-emad-te 0.1.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_emad_te-0.1.0.tar.gz | 2.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| base_emad_te-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.3 kB
Release files / base_emad_te-0.1.0.tar.gz
| Download URL | base_emad_te-0.1.0.tar.gz |
|---|---|
| Size | 2.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ba4ed1649cebbf7ec9222003bc116d839793287979618fc7d7c91184857405e5
|
|
BLAKE2b-256 checksum How to use checksums |
f401f4882a3ab9ccca3e0b1ecd0c8019f6bd32506ef8c848f8267cbc2827970c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Release files / base_emad_te-0.1.0-py3-none-any.whl
| Download URL | base_emad_te-0.1.0-py3-none-any.whl |
|---|---|
| Size | 3.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d02481223da164eed3b5a47fe90213a602774a3b9a81596b0b79f3584b0c49d5
|
|
BLAKE2b-256 checksum How to use checksums |
95e43366bee855c139df80421887014899088f7b04d924eb37814932c7814f4a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Security for base-emad-te 0.1.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.