This release is a pre-release and may not be stable for production use.
UNKNOWN
1 maintainer
Metadata
1 maintainer
Release files for twAjaxTools 0.1a0dev-r3025
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 | |
|---|---|---|---|---|
| twAjaxTools-0.1a0dev-r3025.zip | 21.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| twAjaxTools-0.1a0dev_r3025-py2.4.egg | Legacy Egg format | - | - | Details |
Total release size: 46.2 kB
Release files / twAjaxTools-0.1a0dev-r3025.zip
| Download URL | twAjaxTools-0.1a0dev-r3025.zip |
|---|---|
| Size | 21.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a78c92005e72c0e5f6c217801cdc01dccfb842b84b68990d6ca936960fbab7ef
|
|
BLAKE2b-256 checksum How to use checksums |
c4492cf6670883f2bd70aa0a80060d765ac16bfc421eb4c33d56cc391baf492b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / twAjaxTools-0.1a0dev_r3025-py2.4.egg
| Download URL | twAjaxTools-0.1a0dev_r3025-py2.4.egg |
|---|---|
| Size | 24.7 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
5c250bea49c231cc63d68494735d1e3093ecdb6c6733883b90aa6a9e446c93f4
|
|
BLAKE2b-256 checksum How to use checksums |
00913a908b03e7e5210eb0042536bfe9883510fd7c1abff22574c0fe4dfe57dc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for twAjaxTools 0.1a0dev-r3025
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.
