The author of this package has not provided a project description
Metadata
Release files for aisaplibrary 1.0.22
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 | |
|---|---|---|---|---|
| aisaplibrary-1.0.22.tar.gz | 12.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aisaplibrary-1.0.22-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 26.2 kB
Release files / aisaplibrary-1.0.22.tar.gz
| Download URL | aisaplibrary-1.0.22.tar.gz |
|---|---|
| Size | 12.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
85b7c627e32766f234fb09b1f30d9c2240c4ea95b8c449fad7ced67bcc21928a
|
|
BLAKE2b-256 checksum How to use checksums |
83d50f55f85d9ba5512e41fb00d170ec15502e3a42a4206f49d1d0c8ea6e58aa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.7.4
|
Release files / aisaplibrary-1.0.22-py3-none-any.whl
| Download URL | aisaplibrary-1.0.22-py3-none-any.whl |
|---|---|
| Size | 13.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4d3f5733d5b45614e42c0945fbc0e1b8f6f398a221ffe6ad2da350d70f8d977e
|
|
BLAKE2b-256 checksum How to use checksums |
b96bdd6d0e6aa88e88ff1813f80fbb8842821532b343f56b328bbe0a72edac09
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.7.4
|
Security for aisaplibrary 1.0.22
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.