The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for firsttry-run 0.1.9
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 | |
|---|---|---|---|---|
| firsttry_run-0.1.9.tar.gz | 108.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| firsttry_run-0.1.9-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 214.3 kB
Release files / firsttry_run-0.1.9.tar.gz
| Download URL | firsttry_run-0.1.9.tar.gz |
|---|---|
| Size | 108.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5365c658ba0257914603028f72dd81301e5a82778078e159eec78acc2e6a6d28
|
|
BLAKE2b-256 checksum How to use checksums |
765f98a3ff8c07545605279ad4f4b9fa43fb1ad850d204e8dff804255826741d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.1
|
Release files / firsttry_run-0.1.9-py3-none-any.whl
| Download URL | firsttry_run-0.1.9-py3-none-any.whl |
|---|---|
| Size | 105.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b160e214aac57eabc0489fe5b1bab4cd0857a5ea43cc14fa1c4a9c3690e787ef
|
|
BLAKE2b-256 checksum How to use checksums |
91a4a58030757d7504c5c686c6b15ec1aa1ab4b5aea174be8321dfec96644603
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.1
|
Security for firsttry-run 0.1.9
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.
