Metadata
1 maintainer
Release files for make4db-snowflake 0.1.2
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 | |
|---|---|---|---|---|
| make4db_snowflake-0.1.2.tar.gz | 3.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| make4db_snowflake-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.4 kB
Release files / make4db_snowflake-0.1.2.tar.gz
| Download URL | make4db_snowflake-0.1.2.tar.gz |
|---|---|
| Size | 3.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9dc8421373bcd7ef88b03cc6a284f44f8d3e50f4e79a43a0746eec6a81d9ed0e
|
|
BLAKE2b-256 checksum How to use checksums |
b5d83c9b5e8b06741e10ea83c60a90e16c829291d3403d7cce96fd303d229fdf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.10
|
Release files / make4db_snowflake-0.1.2-py3-none-any.whl
| Download URL | make4db_snowflake-0.1.2-py3-none-any.whl |
|---|---|
| Size | 3.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1fb1ad47317c141da2d24bdd68dbaf19bf8c7831c9d3537eb597c388f160a0cf
|
|
BLAKE2b-256 checksum How to use checksums |
000f8c8540acec33d2ba4a8c0f6b35db258a1aa1b02b42320d351663f5441247
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.10
|
Security for make4db-snowflake 0.1.2
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.
