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