The author of this package has not provided a project description
Metadata
Release files for area-codersao 0.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_codersao-0.1.tar.gz | 1.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| area_codersao-0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.7 kB
Release files / area_codersao-0.1.tar.gz
| Download URL | area_codersao-0.1.tar.gz |
|---|---|
| Size | 1.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b00dc604cecbd24d6f0c10f0eb8871dccdd7501e2e653fce5a0e15ed75edbfdb
|
|
BLAKE2b-256 checksum How to use checksums |
5a005c7d8faa9943368c5d5ef720289830c8ea657f944deee795aed3b9663ef2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Release files / area_codersao-0.1-py3-none-any.whl
| Download URL | area_codersao-0.1-py3-none-any.whl |
|---|---|
| Size | 1.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fa5aa2e3bfb4e3db9a8ba98d9c4d16f551dd5fa2e8e8d9544be811e925d5500f
|
|
BLAKE2b-256 checksum How to use checksums |
29fe173f1b97f5725d675ca9bbbb4a4aa7b09d747716e0f0e0b3575f243ee5ab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Security for area-codersao 0.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.