This release is a pre-release and may not be stable for production use.
The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for archub 1.0.0a8
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 | |
|---|---|---|---|---|
| archub-1.0.0a8.tar.gz | 5.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| archub-1.0.0a8-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 15.8 kB
Release files / archub-1.0.0a8.tar.gz
| Download URL | archub-1.0.0a8.tar.gz |
|---|---|
| Size | 5.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c203e6b15a3c0e3f24f073810ca3870a4e52dbd07b79c9182850681095d46ab0
|
|
BLAKE2b-256 checksum How to use checksums |
314b9ec61a16bd51f24572ed19bc9bab3eca394914e9b755c0f6c3db44cd2440
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / archub-1.0.0a8-py2.py3-none-any.whl
| Download URL | archub-1.0.0a8-py2.py3-none-any.whl |
|---|---|
| Size | 10.0 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
f814b0fdf0b7d41c60574a2b91dd9d5df28993328a14090cf6212e86b89f1029
|
|
BLAKE2b-256 checksum How to use checksums |
72f3aced50926340f3b7fbef8941d202b31f3ce7561f88483aae91819c1511db
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for archub 1.0.0a8
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.
