Interact with the Antimatter Cloud API
Metadata
Release files for antimatter-api 2.0.13
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 | |
|---|---|---|---|---|
| antimatter_api-2.0.13.tar.gz | 172.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| antimatter_api-2.0.13-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 549.6 kB
Release files / antimatter_api-2.0.13.tar.gz
| Download URL | antimatter_api-2.0.13.tar.gz |
|---|---|
| Size | 172.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e5e6652d9a204baa0e596edec188def7d2479490706637d406a4b5256e3d2c1a
|
|
BLAKE2b-256 checksum How to use checksums |
654327277493dc6ad0ca030b95f7916748ff8ae97b4fa8979e08ba9caec7c789
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.3
|
Release files / antimatter_api-2.0.13-py3-none-any.whl
| Download URL | antimatter_api-2.0.13-py3-none-any.whl |
|---|---|
| Size | 377.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
175f744be1a2743eeb276bcfd6926697993502120971f3449019764c1225305e
|
|
BLAKE2b-256 checksum How to use checksums |
87c79af4c4159a6ddec1c356c9cd35cedeb62c618ee0db79b5efea754de06284
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.3
|
Security for antimatter-api 2.0.13
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.