The author of this package has not provided a project description
Metadata
Release files for aclib.inputs 1.0.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 | |
|---|---|---|---|---|
| aclib.inputs-1.0.0.tar.gz | 3.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aclib.inputs-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.5 kB
Release files / aclib.inputs-1.0.0.tar.gz
| Download URL | aclib.inputs-1.0.0.tar.gz |
|---|---|
| Size | 3.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d8a1a5e7f4048f55d95e7050bb51cab51845d09f3d1f57f2f4031a13fe43c1a3
|
|
BLAKE2b-256 checksum How to use checksums |
6f89bc24de4da231c6a8f31db2ca5a3f01a09f817c4476fffdcec285ab7d08e4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.1
|
Release files / aclib.inputs-1.0.0-py3-none-any.whl
| Download URL | aclib.inputs-1.0.0-py3-none-any.whl |
|---|---|
| Size | 3.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d2eaa55cbe5aaf2900cdbd093c74d4366813e33c264ca4f99ccbee93b0cae1c3
|
|
BLAKE2b-256 checksum How to use checksums |
c6cd4800ad3a17a2d2ee682de97f01596ca84c2b12eebe2708aa021629004159
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.1
|
Security for aclib.inputs 1.0.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.