The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for jockbot-nhl 0.0.44
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 | |
|---|---|---|---|---|
| jockbot_nhl-0.0.44.tar.gz | 12.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jockbot_nhl-0.0.44-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 22.3 kB
Release files / jockbot_nhl-0.0.44.tar.gz
| Download URL | jockbot_nhl-0.0.44.tar.gz |
|---|---|
| Size | 12.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
357622350a4e5b5480979c8c631ac031b77b09bb586ba12ddede3695f504f7a5
|
|
BLAKE2b-256 checksum How to use checksums |
0e71c4d9d0d22fc1529785488ffe725c17512a03475ce8e02047f37057bba734
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.8
|
Release files / jockbot_nhl-0.0.44-py3-none-any.whl
| Download URL | jockbot_nhl-0.0.44-py3-none-any.whl |
|---|---|
| Size | 10.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8c2a753762a712757a10ffba72560ab25b05b4abd762bff96da03d71d6063709
|
|
BLAKE2b-256 checksum How to use checksums |
33642c1938cf8f3d972c0c7ca455a957c8ffb39bc14aa0efb93a91a4c1bad140
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.8
|
Security for jockbot-nhl 0.0.44
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.
