The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for orchify 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 | |
|---|---|---|---|---|
| orchify-0.0.1.tar.gz | 37.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| orchify-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 78.5 kB
Release files / orchify-0.0.1.tar.gz
| Download URL | orchify-0.0.1.tar.gz |
|---|---|
| Size | 37.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b83e3a3e9a64329f211f859a8b740e69358d932333172b4f8c31a103280894ff
|
|
BLAKE2b-256 checksum How to use checksums |
b7d0b25e65d7e2dad0847ad4f3c3f9072b5063b83e8a4ffa1c71e5c8e3bd5153
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.3
|
Release files / orchify-0.0.1-py3-none-any.whl
| Download URL | orchify-0.0.1-py3-none-any.whl |
|---|---|
| Size | 41.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
25ee12ded369f543b7b968847ea392e5311d1ca514190d1fd01ad7b2b33b9217
|
|
BLAKE2b-256 checksum How to use checksums |
c5f5a7ee2198ffbb4d613a3ed384b863a6b9da115075b4b69e31f2770d8c9626
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.3
|
Security for orchify 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.
