The author of this package has not provided a project description
Metadata
Release files for ghasedak-otp 0.0.1
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 | |
|---|---|---|---|---|
| ghasedak_otp-0.0.1.tar.gz | 2.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ghasedak_otp-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.8 kB
Release files / ghasedak_otp-0.0.1.tar.gz
| Download URL | ghasedak_otp-0.0.1.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
97befcadda070b3e4744cc3f28dba0e4e4da12b562af58e82345ae559153dfb7
|
|
BLAKE2b-256 checksum How to use checksums |
f4ce44205cdb5ba712404becd090f138e0a18bb73a68b223ee64b66406a72220
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.0
|
Release files / ghasedak_otp-0.0.1-py3-none-any.whl
| Download URL | ghasedak_otp-0.0.1-py3-none-any.whl |
|---|---|
| Size | 3.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7db6d74a65ee097d0cacc4124ccced7ef233e175660d3c85324dac884afac639
|
|
BLAKE2b-256 checksum How to use checksums |
260ffab2cb2440ae5daf1e9e43c09bd2a3772e905663b7318174607b43fd7181
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.0
|
Security for ghasedak-otp 0.0.1
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.