The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for agp-api 0.0.6
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 | |
|---|---|---|---|---|
| agp_api-0.0.6.tar.gz | 7.7 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| agp_api-0.0.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.7 MB
Release files / agp_api-0.0.6.tar.gz
| Download URL | agp_api-0.0.6.tar.gz |
|---|---|
| Size | 7.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d5ac4bef268ddf018464d5b10d7e9183e4b5d61f7885e03cb7ac9628a2fddbf1
|
|
BLAKE2b-256 checksum How to use checksums |
1833d20a0216b5cc079822638c3168d82158558e30aecd26a7b22c8f868a65a4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.1.1 CPython/3.13.0 Windows/11
|
Release files / agp_api-0.0.6-py3-none-any.whl
| Download URL | agp_api-0.0.6-py3-none-any.whl |
|---|---|
| Size | 6.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5fcc42563fb7da7f0e497c93caf582dc87c659076e8f5679740ccd8188f72a03
|
|
BLAKE2b-256 checksum How to use checksums |
4a3f6c81a4d42a7cac3eccceffc710ee30de6f0d5263c2f4e7799570a6ef2ef7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.1.1 CPython/3.13.0 Windows/11
|
Security for agp-api 0.0.6
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.
