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