actex-pay
This name is reserved for the actex agent platform.
The active distribution will be published here once it is ready.
Metadata
Release files for actex-pay 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 | |
|---|---|---|---|---|
| actex_pay-0.0.1.tar.gz | 1.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| actex_pay-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.6 kB
Release files / actex_pay-0.0.1.tar.gz
| Download URL | actex_pay-0.0.1.tar.gz |
|---|---|
| Size | 1.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
626d7becfb1895e68700cf842fb1e17a781dab5295f9c28fecf0adde0413ff75
|
|
BLAKE2b-256 checksum How to use checksums |
d0a996414a159ce9dd28eef7f5f34dd9679d9de7d94fa73650b8676d816d1fb5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.14
|
Release files / actex_pay-0.0.1-py3-none-any.whl
| Download URL | actex_pay-0.0.1-py3-none-any.whl |
|---|---|
| Size | 2.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bffca2c1e83d0a26140f242f452da7559ce43d70307d81c946fd66a6509d19b6
|
|
BLAKE2b-256 checksum How to use checksums |
baecbc7d28cc87f759a07e4ea5f3bdafcdb0ffc0f5f834b15b27bdb1cc912053
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.14
|
Security for actex-pay 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.