The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for orger 0.3.20240826
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 | |
|---|---|---|---|---|
| orger-0.3.20240826.tar.gz | 41.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| orger-0.3.20240826-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 87.7 kB
Release files / orger-0.3.20240826.tar.gz
| Download URL | orger-0.3.20240826.tar.gz |
|---|---|
| Size | 41.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c7cac38d2e52ccf4fba744cf51db6554d23df7c217d69f3d2a0f9ac68e43ff16
|
|
BLAKE2b-256 checksum How to use checksums |
3f7845110be139bf59c8c05eea77adc0f0e8732a855e508463c53a2c65164723
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.8.18
|
Release files / orger-0.3.20240826-py3-none-any.whl
| Download URL | orger-0.3.20240826-py3-none-any.whl |
|---|---|
| Size | 45.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9f26b9bfb519002b2b91a2ab8ff5578177f5985f597138296a7f549668043dd6
|
|
BLAKE2b-256 checksum How to use checksums |
ab8895dc130032efeb3d34688b767e7ed568a5b4944663e67e72f802c6ce979c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.8.18
|
Security for orger 0.3.20240826
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.
