The author of this package has not provided a project description
Metadata
Release files for mjczone-realtime-tokens 0.2.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 | |
|---|---|---|---|---|
| mjczone_realtime_tokens-0.2.1.tar.gz | 8.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mjczone_realtime_tokens-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.6 kB
Release files / mjczone_realtime_tokens-0.2.1.tar.gz
| Download URL | mjczone_realtime_tokens-0.2.1.tar.gz |
|---|---|
| Size | 8.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c918ea591e5a374725217d73090d8da1e02600f741912567007ad0f5ca0f6974
|
|
BLAKE2b-256 checksum How to use checksums |
dfc77780777294756910027fd6b79cfc4cbf68f095c9a081201d14855537eb58
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.8.15
|
Release files / mjczone_realtime_tokens-0.2.1-py3-none-any.whl
| Download URL | mjczone_realtime_tokens-0.2.1-py3-none-any.whl |
|---|---|
| Size | 5.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cbcff7964ac3b73f63ee8de5dadaa89e0dfe011428f2534770aaaa42f14c7d12
|
|
BLAKE2b-256 checksum How to use checksums |
c0889a8e4930512539ef7d16e97d6f3ea2e216afe533d15436c2f6b1a9dccf8d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.8.15
|
Security for mjczone-realtime-tokens 0.2.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.