Metadata
Release files for SCSA 0.1.9
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 | |
|---|---|---|---|---|
| SCSA-0.1.9.tar.gz | 2.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| SCSA-0.1.9-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.8 kB
Release files / SCSA-0.1.9.tar.gz
| Download URL | SCSA-0.1.9.tar.gz |
|---|---|
| Size | 2.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
63c18582963dbc4f36ac2b541c0551d0dfd3f0b68dea60a4b757219424048152
|
|
BLAKE2b-256 checksum How to use checksums |
3908b7b4edd30f7df3d42bc932aa054d3c38e13b3910ac8801936f5d46ce3117
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.6.0 requests-toolbelt/0.9.1 tqdm/4.38.0 CPython/3.8.0
|
Release files / SCSA-0.1.9-py3-none-any.whl
| Download URL | SCSA-0.1.9-py3-none-any.whl |
|---|---|
| Size | 3.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fa1b80381eca7d3a1252599f26224e5edcdf9222a65d5dfdfdbdc6c0d47b9bdc
|
|
BLAKE2b-256 checksum How to use checksums |
eb38163f5f58bc42855da7e5a37cc9899d87c186aa929d82051ea20d55874250
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.6.0 requests-toolbelt/0.9.1 tqdm/4.38.0 CPython/3.8.0
|
Security for SCSA 0.1.9
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.