The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for motherduck 0.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 | |
|---|---|---|---|---|
| motherduck-0.0.0.tar.gz | 1.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| motherduck-0.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.9 kB
Release files / motherduck-0.0.0.tar.gz
| Download URL | motherduck-0.0.0.tar.gz |
|---|---|
| Size | 1.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c32d419fc6210f38c90e44096d907ef8cf4009171fb8a3a6da744e67adbafd49
|
|
BLAKE2b-256 checksum How to use checksums |
f39e302f77db64bdac47776f1b6e5be0e5d685d9c26b278518d74a8e6edc14ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.4
|
Release files / motherduck-0.0.0-py3-none-any.whl
| Download URL | motherduck-0.0.0-py3-none-any.whl |
|---|---|
| Size | 2.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6e5c1184e1de541e653689e0bd1f22039de7bce4efe7d1acee4778fc8ff2dce7
|
|
BLAKE2b-256 checksum How to use checksums |
67cb6b72bb589125107e2cf9f0485bac66c1ef8feaf2fc093b5b03908198b044
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.4
|
Security for motherduck 0.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.
