actex-sdk
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-sdk 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_sdk-0.0.1.tar.gz | 1.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| actex_sdk-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.6 kB
Release files / actex_sdk-0.0.1.tar.gz
| Download URL | actex_sdk-0.0.1.tar.gz |
|---|---|
| Size | 1.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8d0c110cfed5b97300bd359ac99d6992238b0d34659f878bb6c3fc412508f164
|
|
BLAKE2b-256 checksum How to use checksums |
44bb6845407d905b9b6302cc1dbf8709feb5f90fb6ae6245281faa0000674fe4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.14
|
Release files / actex_sdk-0.0.1-py3-none-any.whl
| Download URL | actex_sdk-0.0.1-py3-none-any.whl |
|---|---|
| Size | 2.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f1f602e6ebffa13114e9c4d21413335bc8d114b2b462cc562ecb271d1cac09e3
|
|
BLAKE2b-256 checksum How to use checksums |
a0b5395f42a71232174e2d8ca93f87022af8f9b7184934c1fc7f7565e3609f80
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.14
|
Security for actex-sdk 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.