The author of this package has not provided a project description
Metadata
Release files for jrtd-stock-app 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 | |
|---|---|---|---|---|
| jrtd_stock_app-0.1.tar.gz | 1.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jrtd_stock_app-0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.7 kB
Release files / jrtd_stock_app-0.1.tar.gz
| Download URL | jrtd_stock_app-0.1.tar.gz |
|---|---|
| Size | 1.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a42e8e1f7925f0ea7b6d527a6c0316a551bab8eb32318a786b6c61b5cd106662
|
|
BLAKE2b-256 checksum How to use checksums |
aa8fb26392f9a65adb5050a4fd2641f39741d6a7fb3293fd583240f6ae07e036
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.5
|
Release files / jrtd_stock_app-0.1-py3-none-any.whl
| Download URL | jrtd_stock_app-0.1-py3-none-any.whl |
|---|---|
| Size | 1.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b3ac474dae4944540bdc6802380e3e745a8baa634a871d77b96a26ef373bea03
|
|
BLAKE2b-256 checksum How to use checksums |
042852ab2a4a8b85608cc4c30f4b02f1f80a3658decc7492100760818ed10238
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.5
|
Security for jrtd-stock-app 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.