The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for scdiff 1.1.16
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 | |
|---|---|---|---|---|
| scdiff-1.1.16.tar.gz | 68.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| scdiff-1.1.16-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 126.4 kB
Release files / scdiff-1.1.16.tar.gz
| Download URL | scdiff-1.1.16.tar.gz |
|---|---|
| Size | 68.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4254dd75de7a304bbe87c80f3f9674d7e569d789da71b0a70ced302cbd84ba35
|
|
BLAKE2b-256 checksum How to use checksums |
6db9622481de542ed4ceedec03fb42f55342ec5b0a88dfe20add768eeb5c219f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.9.1
|
Release files / scdiff-1.1.16-py2.py3-none-any.whl
| Download URL | scdiff-1.1.16-py2.py3-none-any.whl |
|---|---|
| Size | 58.1 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
3b4d3759e7bb53085f31c1b1f57b1e62ca688f5c4d1a3e64dd0a10d4c04bc872
|
|
BLAKE2b-256 checksum How to use checksums |
ce83b0a3e48a6b0270a16294900f531258e214baac1c65e9aaaa226f21ff7e6a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.9.1
|
Security for scdiff 1.1.16
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.
