The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for orcadot 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 | |
|---|---|---|---|---|
| orcadot-0.0.0.tar.gz | 667 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| orcadot-0.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.6 kB
Release files / orcadot-0.0.0.tar.gz
| Download URL | orcadot-0.0.0.tar.gz |
|---|---|
| Size | 667 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
782c1af4226b199296a465f2cb236a4e982f699430a6f22747ee235548d2d7cc
|
|
BLAKE2b-256 checksum How to use checksums |
2ddb05a0f280ccfc14d5494945d5596a7bf503f804f39f17188ba13f27854811
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.2
|
Release files / orcadot-0.0.0-py3-none-any.whl
| Download URL | orcadot-0.0.0-py3-none-any.whl |
|---|---|
| Size | 925 Bytes |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ad7d20785718ee00e4e96a8350b4dcab26bb5da61a140252503a3c5708703287
|
|
BLAKE2b-256 checksum How to use checksums |
24a7a586b687078e9601aa0b6b5a17f4aff147c338dad8dad81c4e54e91fc607
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.2
|
Security for orcadot 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.
