Metadata
Release files for xqrcode 1.0.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 | |
|---|---|---|---|---|
| xqrcode-1.0.1.tar.gz | 1.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| xqrcode-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.0 kB
Release files / xqrcode-1.0.1.tar.gz
| Download URL | xqrcode-1.0.1.tar.gz |
|---|---|
| Size | 1.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
44ba32e4333cac503f46a7aa64dfba680f5c559c1ffdfc1ed998dfadb1d60555
|
|
BLAKE2b-256 checksum How to use checksums |
824109593601f50344057f0dee5c6114274af539cba8cd8db9f448c4d5e86606
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.18.4 setuptools/40.6.2 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.7.0
|
Release files / xqrcode-1.0.1-py3-none-any.whl
| Download URL | xqrcode-1.0.1-py3-none-any.whl |
|---|---|
| Size | 3.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4bf79324057e4552c0bb1e081b4cc3574f12771d68c349e6fff8bc317f2785d5
|
|
BLAKE2b-256 checksum How to use checksums |
1aaa3ae894e385542f78e33c00547e42c67b47db18bda3567bc2ef931e0510f5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.18.4 setuptools/40.6.2 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.7.0
|
Security for xqrcode 1.0.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.