Metadata
Release files for ThreadLock 2.13.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 | |
|---|---|---|---|---|
| ThreadLock-2.13.0.zip | 29.7 kB | Without provenance | Details |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ThreadLock-2.13.0-py2.6-win-amd64.egg | Legacy Egg format | - | - | Details |
| ThreadLock-2.13.0-py2.6-win32.egg | Legacy Egg format | - | - | Details |
Total release size: 52.9 kB
Release files / ThreadLock-2.13.0.zip
| Download URL | ThreadLock-2.13.0.zip |
|---|---|
| Size | 29.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
360a2b62238e8d398360ac9588207ffff4d74e1e7ced71cff689022d609330be
|
|
BLAKE2b-256 checksum How to use checksums |
757c7857b254300f65167808e2115e30690bddb5caf67a6d246021dca661d2d2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / ThreadLock-2.13.0-py2.6-win-amd64.egg
| Download URL | ThreadLock-2.13.0-py2.6-win-amd64.egg |
|---|---|
| Size | 11.6 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
7eab60890ce0a58e774c71165ec6980a29baeeb3fccff81238db40c70eee1ba1
|
|
BLAKE2b-256 checksum How to use checksums |
b23d9e215e2a1f15f010eced2ce2b92682c5ae3695484f14ca9c91054eff9e2e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / ThreadLock-2.13.0-py2.6-win32.egg
| Download URL | ThreadLock-2.13.0-py2.6-win32.egg |
|---|---|
| Size | 11.6 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
3f2154884f6f47cf19e8c932172e00e48f3c9b2b96bbf50fa7b6eddaa2fabaa9
|
|
BLAKE2b-256 checksum How to use checksums |
50e34e1e642fefc191aaad268169104ed303c8cdec41d759b71b97d90a55a3df
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for ThreadLock 2.13.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.