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