The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for pycosdk 0.0.10
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 | |
|---|---|---|---|---|
| pycosdk-0.0.10.tar.gz | 37.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pycosdk-0.0.10-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 84.5 kB
Release files / pycosdk-0.0.10.tar.gz
| Download URL | pycosdk-0.0.10.tar.gz |
|---|---|
| Size | 37.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5818b083d7119bc241dec6f93a894eabf12f3fcbb2122fd4e97f18ccda365d23
|
|
BLAKE2b-256 checksum How to use checksums |
f8c7fb4ecb2532492e86a3590e085d2c1bf6aae7223259ef71675f23b9785560
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.12
|
Release files / pycosdk-0.0.10-py3-none-any.whl
| Download URL | pycosdk-0.0.10-py3-none-any.whl |
|---|---|
| Size | 47.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8de94ae66b08ee4d94646a9cd0eebf5f4f610cc84a03efb1b52bb00d11e40938
|
|
BLAKE2b-256 checksum How to use checksums |
20464427237002814fe3e233e14b8965d1ecba64828eb40b4fc29b8601c2191c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.12
|
Security for pycosdk 0.0.10
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.
