The author of this package has not provided a project description
Metadata
Release files for quadkit-sql 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_sql-0.0.1.tar.gz | 380 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| quadkit_sql-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.4 kB
Release files / quadkit_sql-0.0.1.tar.gz
| Download URL | quadkit_sql-0.0.1.tar.gz |
|---|---|
| Size | 380 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ada18ebd2b93eafd82dcc5d397bb8f8ce04ba2776b73133c5e6ad2fd9dedf4c5
|
|
BLAKE2b-256 checksum How to use checksums |
96aa244bbafe05e11183d2b039f7c1f4ea73e9bdefc38bd497b7e57bc482ad35
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.7
|
Release files / quadkit_sql-0.0.1-py3-none-any.whl
| Download URL | quadkit_sql-0.0.1-py3-none-any.whl |
|---|---|
| Size | 985 Bytes |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
40dbd52c69ef2ffdc4d93eef1e9d552a4349faf400d3824e39d096c33d38ece4
|
|
BLAKE2b-256 checksum How to use checksums |
21c62d5fee44642b76402f4dac816518843501c1e46b40a8f5d9e5346c4cf342
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.7
|
Security for quadkit-sql 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.