Enterprise artifact registry supporting 45+ package formats. ## Authentication The JSON management API under `/api/v1/*` accepts **API tokens only as `Authorization: Bearer <token>`**. This is the canonical scheme for programmatic access; JWTs issued by the login flow also use `Bearer`. HTTP Basic credentials on `/api/v1/*` are validated *only* as a real `username:password` login — the password half is **not** retried as an API token. A request to `/api/v1/*` that sends an API token in the password field of Basic auth therefore returns `401 AUTH_ERROR`; switch to `Authorization: Bearer <token>`. Format (package-manager) endpoints such as `/v2/*` (OCI), `/incus/*`, `/debian/*`, and the language registries are intentionally more permissive for client compatibility: in addition to Bearer, they accept HTTP **Basic** auth with the API token supplied in the *password* field (any username), matching the `pip` netrc / Artifactory-style `token:<api_token>` convention used by package managers that cannot send a Bearer header. This Basic-with-token fallback applies to format endpoints only, never to `/api/v1/*`.
1 maintainer
Release files for artifact-keeper-client 1.6.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 | |
|---|---|---|---|
| artifact_keeper_client-1.6.0.tar.gz | 422.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| artifact_keeper_client-1.6.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.6 MB
Release files / artifact_keeper_client-1.6.0.tar.gz
| Download URL | artifact_keeper_client-1.6.0.tar.gz |
|---|---|
| Size | 422.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4e324cfa5fa91c2388aad6816ed13265e7c9557c2cbb0b06d8d6d9921e4540fc
|
|
BLAKE2b-256 checksum How to use checksums |
5d537bcd9f447e24cc36d5e91113583e783cf8e89142f9fa2b4b9f65421a6faf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 19, 2026.
Transparency logRelease files / artifact_keeper_client-1.6.0-py3-none-any.whl
| Download URL | artifact_keeper_client-1.6.0-py3-none-any.whl |
|---|---|
| Size | 1.1 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
851fc2f50295414579c510796bbaab1d46c55a6756d69f473c98ecb99a9f6de6
|
|
BLAKE2b-256 checksum How to use checksums |
7a30e951a60d558f6add90e1a1f0e5310a480a8b2ae7f88f6e962cb367ed30ec
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 19, 2026.
Transparency log
