The author of this package has not provided a project description
Metadata
Release files for doc-store-client 0.1.101
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 | |
|---|---|---|---|---|
| doc_store_client-0.1.101.tar.gz | 29.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| doc_store_client-0.1.101-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 49.2 kB
Release files / doc_store_client-0.1.101.tar.gz
| Download URL | doc_store_client-0.1.101.tar.gz |
|---|---|
| Size | 29.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
091fca9b1e0816938477de3670d6e95c0f458f81c4416bd1de7255ec32e75b3a
|
|
BLAKE2b-256 checksum How to use checksums |
47ec7891e44b488a74a70d55b3b4b5881581551f5cfb9e779973e5f049fd89af
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Release files / doc_store_client-0.1.101-py3-none-any.whl
| Download URL | doc_store_client-0.1.101-py3-none-any.whl |
|---|---|
| Size | 20.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
20c07b10a0d7ce14bf78cf77aa31a0cd9a818140dd741a6a64988b486cfcb273
|
|
BLAKE2b-256 checksum How to use checksums |
a66f11eac98422b7095509c0c992ea0b0a5729bb02bdf635c5835a8ec0963d0e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Security for doc-store-client 0.1.101
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.