The author of this package has not provided a project description
Metadata
Release files for databridgex 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 | |
|---|---|---|---|---|
| databridgex-0.0.0.tar.gz | 824 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| databridgex-0.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.0 kB
Release files / databridgex-0.0.0.tar.gz
| Download URL | databridgex-0.0.0.tar.gz |
|---|---|
| Size | 824 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a8d557bf7cfc67135ef0d8ba5f97ea4edf4373ebec4e97726ba744273e2f9c6c
|
|
BLAKE2b-256 checksum How to use checksums |
616d3ad0fa98439e227744d11e8342c31577baa0c5c92555559286bc14a7e029
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.10.12
|
Release files / databridgex-0.0.0-py3-none-any.whl
| Download URL | databridgex-0.0.0-py3-none-any.whl |
|---|---|
| Size | 1.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8960a22bdcfb63696a07ff4d2b0fea4fd4ef2e4188dace67e1a2ec4e6b07e041
|
|
BLAKE2b-256 checksum How to use checksums |
44b024f352aec08cd6f83486fcb61dbfc5656256ab8c8683bb5b6b8c97651db4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.10.12
|
Security for databridgex 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.