The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for quadkit-auth 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 | |
|---|---|---|---|---|
| quadkit_auth-0.0.1.tar.gz | 382 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| quadkit_auth-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.4 kB
Release files / quadkit_auth-0.0.1.tar.gz
| Download URL | quadkit_auth-0.0.1.tar.gz |
|---|---|
| Size | 382 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
325aff6df58d3283f774a5ecf0743adb4ac5d0ac5a53520c4d6541b47bb4fe99
|
|
BLAKE2b-256 checksum How to use checksums |
7a2389e2538cb3f4b820168040843af79e31847688100399978ab7f18a226e05
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.7
|
Release files / quadkit_auth-0.0.1-py3-none-any.whl
| Download URL | quadkit_auth-0.0.1-py3-none-any.whl |
|---|---|
| Size | 995 Bytes |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
02596055b6f65427660f8f904040c82ea9a2be507d1cda620a50a07cec03b6f7
|
|
BLAKE2b-256 checksum How to use checksums |
42f907e24ee7f99480888d7717d8a196702c6cf3ff5466d0d84fedf3e1692551
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.7
|
Security for quadkit-auth 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.
