The author of this package has not provided a project description
Metadata
Release files for orger 0.3.20231005
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.20231005.tar.gz | 38.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| orger-0.3.20231005-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 81.7 kB
Release files / orger-0.3.20231005.tar.gz
| Download URL | orger-0.3.20231005.tar.gz |
|---|---|
| Size | 38.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8d39337f72829d93e7baa9e759d978a93a0b5032082270121f4b26e0bdfb32d3
|
|
BLAKE2b-256 checksum How to use checksums |
6c03b9d8a83acf9541fa21bff8db90d00725edcc0d3c60e7d8fc3c1ef002226c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.18
|
Release files / orger-0.3.20231005-py3-none-any.whl
| Download URL | orger-0.3.20231005-py3-none-any.whl |
|---|---|
| Size | 42.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
738ad7ac48d70635ffd26728ddcd1500377beeac152c21ae5d80100583a8ac69
|
|
BLAKE2b-256 checksum How to use checksums |
2278ffd4c7b5b23efc0b123464c13323b18861ca0462c5cd55fcd0cc65b046e6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.18
|
Security for orger 0.3.20231005
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.