The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for dbrecord 1.1.4
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 | |
|---|---|---|---|---|
| dbrecord-1.1.4.tar.gz | 7.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dbrecord-1.1.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 27.8 kB
Release files / dbrecord-1.1.4.tar.gz
| Download URL | dbrecord-1.1.4.tar.gz |
|---|---|
| Size | 7.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3afc0013102ea1404e885575135ae7f35a6e59115b4fd9b8aed2423a10f62d58
|
|
BLAKE2b-256 checksum How to use checksums |
dfc9766bb6184b35a4f25d28ff6f33b585d50c3dee4a8ce48a664c13105e7468
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.9
|
Release files / dbrecord-1.1.4-py3-none-any.whl
| Download URL | dbrecord-1.1.4-py3-none-any.whl |
|---|---|
| Size | 20.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7ae7bc674ed6d2fe5785bf3c48a9dbf8008fb8271cc900dc7711b3b7bdb0eb45
|
|
BLAKE2b-256 checksum How to use checksums |
f2993b7852bfeeb675fb552efbb282b5c9eed04d7c777c0f2beeb9e24513daa8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.9
|
Security for dbrecord 1.1.4
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.
