The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for kubiq-apm 1.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 | |
|---|---|---|---|---|
| kubiq_apm-1.0.0.tar.gz | 2.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kubiq_apm-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.1 kB
Release files / kubiq_apm-1.0.0.tar.gz
| Download URL | kubiq_apm-1.0.0.tar.gz |
|---|---|
| Size | 2.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8ac6acae60bd99c984e385e51bed7672b9499d17bce1eb2b669ac799170b9b7e
|
|
BLAKE2b-256 checksum How to use checksums |
812a3bf6902215727488e62a7419d945c3e705a82c2e6ca6fd2d903f03451027
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.13
|
Release files / kubiq_apm-1.0.0-py3-none-any.whl
| Download URL | kubiq_apm-1.0.0-py3-none-any.whl |
|---|---|
| Size | 2.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5057402fd57b01125238c84cb8f3e1be087fe85e8d43716854d0e1b33828e3d0
|
|
BLAKE2b-256 checksum How to use checksums |
b0654d216b1f01caa54942ea4369a8ff2ae8da1c63e1ffb8c48bc87a0b251ba3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.13
|
Security for kubiq-apm 1.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.
