The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for squimple 0.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 | |
|---|---|---|---|---|
| squimple-0.0.1.tar.gz | 618.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| squimple-0.0.1-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 1.1 MB
Release files / squimple-0.0.1.tar.gz
| Download URL | squimple-0.0.1.tar.gz |
|---|---|
| Size | 618.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
529254a20f0287d47b52da45dd4937f4e257766e2061eb962198b30c30ee32fa
|
|
BLAKE2b-256 checksum How to use checksums |
eb7e95a40448ba84f65ce92bcc6bce7d595ee637a28a281915788a8e04a60e9b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.25.1
|
Release files / squimple-0.0.1-py2.py3-none-any.whl
| Download URL | squimple-0.0.1-py2.py3-none-any.whl |
|---|---|
| Size | 437.7 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
230acaa4c95a47849113c1e52e918ef1e0bf390f26ed3d8fa8c4555a3c736a80
|
|
BLAKE2b-256 checksum How to use checksums |
58654233ec9d5cd19345c54599655c9a690eeb622e075b5506a37f6d8b6d0485
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.25.1
|
Security for squimple 0.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.
