The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for area-mehak 0.1.1
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 | |
|---|---|---|---|---|
| area_mehak-0.1.1.tar.gz | 1.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| area_mehak-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.8 kB
Release files / area_mehak-0.1.1.tar.gz
| Download URL | area_mehak-0.1.1.tar.gz |
|---|---|
| Size | 1.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
967e07a11cd460694a0657ee6a910a1398973ab72c80b7a6bc98e1b4fca00093
|
|
BLAKE2b-256 checksum How to use checksums |
efafac315d0e556cae11a24cdb6140422934b91b1b93212b227e1b4fbc64d2da
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.0
|
Release files / area_mehak-0.1.1-py3-none-any.whl
| Download URL | area_mehak-0.1.1-py3-none-any.whl |
|---|---|
| Size | 1.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
29df97364bdb5abeff7db4499d27b1d81df43b3c05199fb89e14a0e293244823
|
|
BLAKE2b-256 checksum How to use checksums |
b4515da698f276251297d13388d7bcd8f85e33e036811b3a776bb192a369d66b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.0
|
Security for area-mehak 0.1.1
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.
