1 maintainer
Metadata
1 maintainer
Release files for accessPolygon 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 | |
|---|---|---|---|---|
| accessPolygon-0.1.0.tar.gz | 4.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| accessPolygon-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.7 kB
Release files / accessPolygon-0.1.0.tar.gz
| Download URL | accessPolygon-0.1.0.tar.gz |
|---|---|
| Size | 4.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1e2a40e81859a75e161230890dbf86300094a06c60cc8606be06e4aa31caf09c
|
|
BLAKE2b-256 checksum How to use checksums |
fdef2fee35f3df89d9759c9b35140598950ddd245f612f1ca61dffb2ddd24c29
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.7.2
|
Release files / accessPolygon-0.1.0-py3-none-any.whl
| Download URL | accessPolygon-0.1.0-py3-none-any.whl |
|---|---|
| Size | 5.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e959f8ef73ba2427a38326b8f7818600c54ee9effedee75e6801cdcdae49f4ad
|
|
BLAKE2b-256 checksum How to use checksums |
6ac844311ea8ff53c0e710bd28db2d18610eb006df37f4b253a3c307c23453b5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.7.2
|
Security for accessPolygon 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.
