The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for oqd-trical 0.0.0
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 | |
|---|---|---|---|---|
| oqd_trical-0.0.0.tar.gz | 2.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| oqd_trical-0.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.8 kB
Release files / oqd_trical-0.0.0.tar.gz
| Download URL | oqd_trical-0.0.0.tar.gz |
|---|---|
| Size | 2.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
03a11df4212ff8e4768ddf9e5d628df7a556c552aa7860b99bb9641cd700d32a
|
|
BLAKE2b-256 checksum How to use checksums |
e87e375c7d01f39549b93fa582d6afea54c44d270d7f82ab1e53ba6935e000c5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.1
|
Release files / oqd_trical-0.0.0-py3-none-any.whl
| Download URL | oqd_trical-0.0.0-py3-none-any.whl |
|---|---|
| Size | 1.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
88960b96b1a108a2c7f72f98da08b013c8e8eb08db8b415254b056bcdd0bc890
|
|
BLAKE2b-256 checksum How to use checksums |
559be19f55797c848082f8706f4e31ceecc1a847421a4d92c09035c851dc68f7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.1
|
Security for oqd-trical 0.0.0
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.
