The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for Authwave 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 | |
|---|---|---|---|---|
| Authwave-0.0.1.tar.gz | 10.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| Authwave-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 28.8 kB
Release files / Authwave-0.0.1.tar.gz
| Download URL | Authwave-0.0.1.tar.gz |
|---|---|
| Size | 10.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2074d2ee406c8138b248ab5bc03bc9690a7ae3aee1e646078c7f91aac9c1c141
|
|
BLAKE2b-256 checksum How to use checksums |
df601756e4864514a5db0a68c9e720ec53ce21b2d3ca69649bbd654eb4791b0e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.4
|
Release files / Authwave-0.0.1-py3-none-any.whl
| Download URL | Authwave-0.0.1-py3-none-any.whl |
|---|---|
| Size | 18.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cfa8ae0725fbb91a76d93bb5a75c2e01dcebf71ebee617aa123496e1eb4c47a7
|
|
BLAKE2b-256 checksum How to use checksums |
4beab5157855046e598e907ac507fbb55cb54f8445f160033a6e798c54890a06
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.4
|
Security for Authwave 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.
