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