The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for common-as 1.3.2
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 | |
|---|---|---|---|---|
| common_as-1.3.2.tar.gz | 21.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| common_as-1.3.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 47.9 kB
Release files / common_as-1.3.2.tar.gz
| Download URL | common_as-1.3.2.tar.gz |
|---|---|
| Size | 21.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1c728f5da9368890e78f44d32294ff9ea6454deb775a28f5e922c2b450203608
|
|
BLAKE2b-256 checksum How to use checksums |
c5e5c06ca5e4423f7f162bf35357bc624695c27d5bc6b68969dc2f3ec531565e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.13
|
Release files / common_as-1.3.2-py3-none-any.whl
| Download URL | common_as-1.3.2-py3-none-any.whl |
|---|---|
| Size | 26.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
77fada9c7f2cf2a3e6a724c502f44e45ca1548e87b83e04255eb9c2e21c403ff
|
|
BLAKE2b-256 checksum How to use checksums |
44364ade31ea92e3c8594c093d4b1856f1c628c80419c2ae96717957dca0a967
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.13
|
Security for common-as 1.3.2
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.
