The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for dps-otp 0.0.2
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 | |
|---|---|---|---|---|
| dps_otp-0.0.2.tar.gz | 5.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dps_otp-0.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.9 kB
Release files / dps_otp-0.0.2.tar.gz
| Download URL | dps_otp-0.0.2.tar.gz |
|---|---|
| Size | 5.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5640f784c39c4478b6d520e5f9a72c7f9c63cc5b2119ddb54c31245b2329ef17
|
|
BLAKE2b-256 checksum How to use checksums |
fb11fa82a2f5e9139bb056bc1b7d97bf178de26eb3bf985d94240dea8432c262
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.0
|
Release files / dps_otp-0.0.2-py3-none-any.whl
| Download URL | dps_otp-0.0.2-py3-none-any.whl |
|---|---|
| Size | 5.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2d80fe06a093a22dac1c15a8e634f3c725086c7ab025dc9e9b001877a38d5f49
|
|
BLAKE2b-256 checksum How to use checksums |
7b21e17e2a1a45f0ea7fc05d34cb17061c5a92cd78f80a4156aac8a9a6400de0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.0
|
Security for dps-otp 0.0.2
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.
