The author of this package has not provided a project description
Metadata
Release files for asa-license 0.0.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 | |
|---|---|---|---|---|
| asa_license-0.0.1.tar.gz | 747 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| asa_license-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.7 kB
Release files / asa_license-0.0.1.tar.gz
| Download URL | asa_license-0.0.1.tar.gz |
|---|---|
| Size | 747 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cdede50769352fea5e1d50d11c872a1313e06df4040e31c06fe515899b2bf31c
|
|
BLAKE2b-256 checksum How to use checksums |
6a14510af38a78dabbb8fdf277cab156baa156c04af96430215454ae5dc721bd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.3
|
Release files / asa_license-0.0.1-py3-none-any.whl
| Download URL | asa_license-0.0.1-py3-none-any.whl |
|---|---|
| Size | 963 Bytes |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
46ebedc1deb4283da3c72209864b3485ca3b866853af3f1ffd809ebf79c3e172
|
|
BLAKE2b-256 checksum How to use checksums |
b8cd4a7a521584e31b9ac334020e1c94c0971d877b96a4414d032b9262f06083
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.3
|
Security for asa-license 0.0.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.