The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for atp-core 2.0.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 | |
|---|---|---|---|---|
| atp_core-2.0.0.tar.gz | 4.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| atp_core-2.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.6 kB
Release files / atp_core-2.0.0.tar.gz
| Download URL | atp_core-2.0.0.tar.gz |
|---|---|
| Size | 4.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9792db8b3bfcce486cf9067dc261db479aee02d2ce1965f3bfe872b99f3bace3
|
|
BLAKE2b-256 checksum How to use checksums |
f73ac9c9c0c980a23de42a2859ca1e91c7aa56d5d7e81bc1384c98796f751254
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.4
|
Release files / atp_core-2.0.0-py3-none-any.whl
| Download URL | atp_core-2.0.0-py3-none-any.whl |
|---|---|
| Size | 5.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e6b6c2b659917d45f163871ad89892a53728c82e03900c85e3c05afaa5c06ba8
|
|
BLAKE2b-256 checksum How to use checksums |
ed3a8f21b389db153b30d67fdd91190739bd9d4b434e61410c5cb17f3327bf70
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.4
|
Security for atp-core 2.0.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.
