The author of this package has not provided a project description
Metadata
Release files for microsoft-365-emad 0.1.4
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 | |
|---|---|---|---|---|
| microsoft_365_emad-0.1.4.tar.gz | 12.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| microsoft_365_emad-0.1.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 28.6 kB
Release files / microsoft_365_emad-0.1.4.tar.gz
| Download URL | microsoft_365_emad-0.1.4.tar.gz |
|---|---|
| Size | 12.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
70c79ff27aeb0b8da17b533c01fca10de89c4c105edd2a527cc84e3ff14880f1
|
|
BLAKE2b-256 checksum How to use checksums |
9686fae6ffbc8700dd4cda68f3c64abbac28cff87921fe3a392185528c5d68b8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Release files / microsoft_365_emad-0.1.4-py3-none-any.whl
| Download URL | microsoft_365_emad-0.1.4-py3-none-any.whl |
|---|---|
| Size | 16.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
339f3ff2f5f6dc8facc30e64d555be2840b2b674341d1c0879ddc81504461eaf
|
|
BLAKE2b-256 checksum How to use checksums |
034102eb91b3762f1cbf243b69608f0c4150a643582003ddd29f9a2f0d6551de
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Security for microsoft-365-emad 0.1.4
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.