The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for Astock 0.1.3
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 | |
|---|---|---|---|---|
| Astock-0.1.3.tar.gz | 193.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| Astock-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 394.5 kB
Release files / Astock-0.1.3.tar.gz
| Download URL | Astock-0.1.3.tar.gz |
|---|---|
| Size | 193.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b7165e0159a95cabb97c480d8a24eeeadb455a15d0778f34f30cea1229cd4a5e
|
|
BLAKE2b-256 checksum How to use checksums |
e2570ff5eddc47031173f4422cf3f593e484c0d68776f5a9c2a2022b46276916
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.7.16
|
Release files / Astock-0.1.3-py3-none-any.whl
| Download URL | Astock-0.1.3-py3-none-any.whl |
|---|---|
| Size | 200.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a1d6f62ab1d2464303e0ea9dab6524592673c3ec84a3d20827db4207f1e9f83c
|
|
BLAKE2b-256 checksum How to use checksums |
a07f0c1d1de4213411022137cab4cbe2d394d054d84aa0850a1d2f31f05971a9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.7.16
|
Security for Astock 0.1.3
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.
