The author of this package has not provided a project description
Metadata
Release files for authflow-sdk 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 | |
|---|---|---|---|---|
| authflow_sdk-1.0.0.tar.gz | 5.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| authflow_sdk-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.8 kB
Release files / authflow_sdk-1.0.0.tar.gz
| Download URL | authflow_sdk-1.0.0.tar.gz |
|---|---|
| Size | 5.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d66c5b22c2cd47ded2ae0c84b3b817d0a430e43fb636c0f6dad96e48f3b462a8
|
|
BLAKE2b-256 checksum How to use checksums |
93823a0107eb0bec47291d98147a439733bf3f205345418ddb6e704371094a79
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.2
|
Release files / authflow_sdk-1.0.0-py3-none-any.whl
| Download URL | authflow_sdk-1.0.0-py3-none-any.whl |
|---|---|
| Size | 3.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
27d292eed3eeb6f56bf1943b8f20e86b7d4c3d6a36291757e3616c7bb999245f
|
|
BLAKE2b-256 checksum How to use checksums |
f26b0c45ca69880c7607b89e824ca43ef712e621e701081b4b486aca1f657006
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.2
|
Security for authflow-sdk 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.