1 maintainer
Metadata
1 maintainer
Release files for jstimer4py 0.1.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 | |
|---|---|---|---|---|
| jstimer4py-0.1.1.tar.gz | 3.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jstimer4py-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.4 kB
Release files / jstimer4py-0.1.1.tar.gz
| Download URL | jstimer4py-0.1.1.tar.gz |
|---|---|
| Size | 3.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7e94470065f5957c48c9522681592a62aba27c25c87953ed5aba08af9ec0ae5a
|
|
BLAKE2b-256 checksum How to use checksums |
b8541157f2ff1e0b962324d7bcf8b6ec25d8f7c611e541c5a295fc6fb4aa4763
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.7.1 CPython/3.11.6 Linux/6.7.2-zen1-2-zen
|
Release files / jstimer4py-0.1.1-py3-none-any.whl
| Download URL | jstimer4py-0.1.1-py3-none-any.whl |
|---|---|
| Size | 3.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
847876217cd56d8ce593c6e9a41d2332e2e0ebd42c6a3f88bfca6c0139ce95e2
|
|
BLAKE2b-256 checksum How to use checksums |
ca21c71606b7cbb243f33f3010f3e2b18766813a4dbfb89d91ae7f6eb511ea1d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.7.1 CPython/3.11.6 Linux/6.7.2-zen1-2-zen
|
Security for jstimer4py 0.1.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.
