The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for area-lib 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 | |
|---|---|---|---|---|
| area_lib-0.1.0.tar.gz | 869 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| area_lib-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.9 kB
Release files / area_lib-0.1.0.tar.gz
| Download URL | area_lib-0.1.0.tar.gz |
|---|---|
| Size | 869 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
07daf02bd3c7d186c986a457d44475c1d22c4770e81dea09dd52697804afe2ba
|
|
BLAKE2b-256 checksum How to use checksums |
aa0ddd2ce5d8413ca247327b5b7752360cbfc35c07c0a39e3f2a37e860b7b2fe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.19
|
Release files / area_lib-0.1.0-py3-none-any.whl
| Download URL | area_lib-0.1.0-py3-none-any.whl |
|---|---|
| Size | 1.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7093cc92bfabde58877952fd1d0640b18989bd34e700c6abe9c776a651da4d3b
|
|
BLAKE2b-256 checksum How to use checksums |
a1a33c4a6c96993714e7a2c1dbe4cf62a21990a621767cdba90d1a027535dd7f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.19
|
Security for area-lib 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.
