keyrings.google-artifactregistry-auth

What it is and what it does

This package is a keyring backend plugin that bridges Google Cloud authentication and Python package management tools. It integrates with the keyring library to automatically supply credentials when pip or twine interact with private Python repositories hosted on Google Cloud Artifact Registry. The backend searches for credentials in a defined order: first Google Application Default Credentials, then the gcloud SDK's cached access token. Once installed and configured, it handles authentication transparently—pip and twine read the credentials from keyring without requiring manual token management.

The package is designed for teams using Google Cloud infrastructure who want to host private Python packages on Artifact Registry. It works with standard Python packaging tools by registering itself as a keyring backend with priority 9, and it integrates with tox via the `requires` directive to ensure credentials are available before private dependencies are installed. The setup requires configuring `.pypirc` or `pip.conf` with your Artifact Registry repository URL, then installing this package to activate automatic authentication.

Use it for:

• Authenticate pip to install private Python packages from Google Cloud Artifact Registry without manual token entry.
• Use twine to publish packages to Artifact Registry with automatic credential resolution from gcloud or service account keys.
• Bootstrap tox environments with credential support so private dependencies can be installed during test runs.
• Manage multiple Artifact Registry repositories across projects using Application Default Credentials or gcloud login.
• Integrate Artifact Registry authentication into CI/CD pipelines using service account JSON keys via GOOGLE_APPLICATION_CREDENTIALS.

Worth the install?

AI-flagged interpretation of the facts on this page — verify before relying

A keyring backend that authenticates to Google Cloud Artifact Registry using Application Default Credentials or gcloud SDK tokens, enabling pip and twine to access private Python repositories.

Yes, if you use Google Cloud Artifact Registry for private Python packages and want seamless credential integration with pip and twine. The package is stable and has low install friction, but note that maintenance is aging (last release March 2023, no updates since April 2025). Verify compatibility with your current versions of keyring and google-auth before relying on it in production; consider monitoring the repository for security updates or maintenance signals.

Install

keyrings-google-artifactregistry-auth on PyPI

pip install keyrings-google-artifactregistry-auth

uv add keyrings-google-artifactregistry-auth

poetry add keyrings-google-artifactregistry-auth

Installing keyrings.google-artifactregistry-auth

Before you install

Low install friction with four straightforward runtime dependencies. Maintenance status is aging—last release was in March 2023 and the repository has not been updated since April 2025, though it remains unarchived and the package is marked Production/Stable.

License in practice

Licensed under Apache Software License (permissive), so you can use, modify, and distribute it freely with minimal restrictions.

Quickstart

pip install keyrings.google-artifactregistry-auth

# Verify installation
keyring --list-backends

# Then configure .pypirc or pip.conf with your Artifact Registry URL
# and use pip/twine normally—credentials are resolved automatically

Requires gcloud SDK to be installed and configured, or GOOGLE_APPLICATION_CREDENTIALS environment variable set to a service account JSON key file.

Verify before relying

• Whether the package works with current versions of keyring and google-auth given the aging maintenance status.
• Compatibility with modern Python versions beyond the stated >=3.6 requirement.

Package facts

Evidence: keyrings.google_artifactregistry_auth-1.1.2-py3-none-any.whl

Tags

More Security packages