The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for as-common 0.9.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 | |
|---|---|---|---|---|
| as_common-0.9.1.tar.gz | 1.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| as_common-0.9.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.6 kB
Release files / as_common-0.9.1.tar.gz
| Download URL | as_common-0.9.1.tar.gz |
|---|---|
| Size | 1.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
06a861f268fc238b6f121202c7ee5796cc885ae5e32b9fd01cdf1b715c67767d
|
|
BLAKE2b-256 checksum How to use checksums |
5de34c847af7b1dc7b48516f9a2b644a01be883e4da3f664e3ff9a8ce063a968
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.13
|
Release files / as_common-0.9.1-py3-none-any.whl
| Download URL | as_common-0.9.1-py3-none-any.whl |
|---|---|
| Size | 1.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9b321bc115d7bdae3b8510a6f45ad22adecf4e96cbe00c84413e7c9f69f60257
|
|
BLAKE2b-256 checksum How to use checksums |
df8fb778b273e318d77c643e5117dac180295fae5708dd70a3ca589d01929203
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.13
|
Security for as-common 0.9.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.
