The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for amplify-auth 0.1.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 | |
|---|---|---|---|---|
| amplify_auth-0.1.1.tar.gz | 7.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| amplify_auth-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.1 kB
Release files / amplify_auth-0.1.1.tar.gz
| Download URL | amplify_auth-0.1.1.tar.gz |
|---|---|
| Size | 7.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
44713823511bfba38cbe4fbc81730077089ba9e516f513b74574205d770085e3
|
|
BLAKE2b-256 checksum How to use checksums |
36c94731e365912b0bc6ffe4f4593fcca89867b7abaec15c009130a4001d4e8b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.14
|
Release files / amplify_auth-0.1.1-py3-none-any.whl
| Download URL | amplify_auth-0.1.1-py3-none-any.whl |
|---|---|
| Size | 5.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e289451f7df6e5dda67963ea35c1b722af14c2d64d35d4060326da80a498271d
|
|
BLAKE2b-256 checksum How to use checksums |
f8838fad21af0ca024ff14c2cd658a0660fd3b8f000cf20d1bc7efb2a94eed9b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.14
|
Security for amplify-auth 0.1.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.
