1 maintainer
Metadata
1 maintainer
Release files for example-project-orl 2.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 | |
|---|---|---|---|---|
| example_project_orl-2.0.0.tar.gz | 26.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| example_project_orl-2.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 30.4 kB
Release files / example_project_orl-2.0.0.tar.gz
| Download URL | example_project_orl-2.0.0.tar.gz |
|---|---|
| Size | 26.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dcdfb4a2800f549be8d80de7484d7eaead3de090d45ff5a1ae5fa15c28c66cf3
|
|
BLAKE2b-256 checksum How to use checksums |
a1285f77b3246e0953161cf1abb18fb600292d2b7fd5c8bafd8e4e05cc5e80f0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Release files / example_project_orl-2.0.0-py3-none-any.whl
| Download URL | example_project_orl-2.0.0-py3-none-any.whl |
|---|---|
| Size | 4.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
202555617eb6b2bd1772fc7ff1fa6f674fb22f0cc22fb05a6428865f84ff0e9b
|
|
BLAKE2b-256 checksum How to use checksums |
7d967c16cceb487d4c1c4703887f69b9c1a2a325ffcb248ea392e28aa6b77176
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Security for example-project-orl 2.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.
