The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for databuild-core 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 | |
|---|---|---|---|---|
| databuild_core-0.0.1.tar.gz | 375 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| databuild_core-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.4 kB
Release files / databuild_core-0.0.1.tar.gz
| Download URL | databuild_core-0.0.1.tar.gz |
|---|---|
| Size | 375 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
37b1bfb1d6fee19e9023a9314e854ca01907992335f0029bdcc079f046a52469
|
|
BLAKE2b-256 checksum How to use checksums |
43784b0d5c153c7693b4c348af5c7f42ce9a97b8e6d6a165ff268496d852279f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Release files / databuild_core-0.0.1-py3-none-any.whl
| Download URL | databuild_core-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
76363b5dee7172726fc264a8bdc5a62aab7201b8714baf835cdcf737ccfea597
|
|
BLAKE2b-256 checksum How to use checksums |
1765aeed84d48ea77c2804cc46df802bdd9f6657816379d04d93669c866f294f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Security for databuild-core 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.
