Automic VaultAutomic Vault

brew

Install keyring with Homebrew

Easy way to access the system keyring service from python. Version 25.7.0 via Homebrew; verified from local package data.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install keyring

local Homebrew formula metadata

overview

Package summary

Easy way to access the system keyring service from python

Commands and aliases

  • keyring

history

Project history and usage

Python keyring is the common Python library and command-line tool for storing and retrieving secrets through the operating system credential store. It gives Python applications one API over macOS Keychain, Freedesktop Secret Service/libsecret, KDE KWallet, Windows Credential Manager, and extension backends.

Project history

The project began as python-keyring-lib and later settled into the jaraco/keyring repository. A 2014 maintainer announcement moved hosting from Bitbucket to GitHub, preserving issues and source history while aligning development with GitHub and Travis CI workflows of that period.

The project steadily narrowed and modularized its backend surface. Less preferred or risky backends were split into keyrings.alt, while the main package concentrated on recommended system keyrings and a CLI/API that applications could call safely.

Adoption history

keyring became infrastructure in the Python packaging and developer-tools ecosystem because tools can use it for credentials without inventing their own password storage. PyPI release history, Read the Docs documentation, and downstream packages show a long-lived library with regular maintenance across Python and operating-system changes.

How it is used

Applications call keyring.set_password, get_password, or credential APIs, while users can invoke the keyring command to inspect or manage secrets. The package chooses a viable backend for the environment, and users can configure explicit backends through keyringrc.cfg when automatic selection is not enough.

Why package nerds care

keyring is small but central because it connects Python packaging, CLIs, desktop secret stores, and enterprise artifact repositories. It is also a useful example of packaging security posture: plaintext and weaker backends were moved to an alternate package rather than silently remaining first-class defaults.

Timeline

  • 2014: The maintainer announced the move from Bitbucket to GitHub under jaraco/keyring.
  • 2010s: The project supported the major desktop credential stores through a unified Python API.
  • 2017: Legacy and less preferred backends were split toward keyrings.alt, reducing the default backend surface.
  • 2024: v24 removed older macOS and utility modules while retaining the main credential-store API.
  • 2025: v25 releases continued backend and CLI maintenance, including KWallet 6 support.

Related projects

  • Related projects include keyrings.alt for alternate backends, SecretStorage/libsecret for Linux Secret Service integration, pywin32-ctypes for Windows credential access, KWallet bindings, pip/twine-style packaging clients, and cloud artifact-registry keyring plugins.

security posture

Risk level: green

narrow executable package without higher-risk signals.

Risk classifier

green risk · low confidence · appliance

Why

  • narrow executable package without higher-risk signals

Signals

  • metadata:no-higher-risk-signals

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 6 platform targets.
  • Installs with 1 runtime dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix
keyringrc.cfg

executables

Installed executables

CommandKindExposureNote
keyringcliglobal executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08
manager version25.7.0
manager updated
local dataok
upstreamnot checked
latest detectednot detected

https://github.com/jaraco/keyring

  • infoNo package-manager update timestamp was available.low confidence
  • infoNo cached GitHub release or tag data was available.https://github.com/jaraco/keyringnone confidence

install metadata

Package metadata

Package keybrew:keyring
Version25.7.0
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/keyring
Homepagehttps://github.com/jaraco/keyring
Repositoryhttps://github.com/jaraco/keyring
Upstream docshttps://keyring.readthedocs.io/en/latest
LicenseMIT
Source archivehttps://files.pythonhosted.org/packages/43/4b/674af6ef2f97d56f0ab5153bf0bfa28ccb6c3ed4d1babf4305449668807b/keyring-25.7.0.tar.gz
Dependenciespython@3.14
Bottleavailable (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namekeyring
Version Scheme0
Revision1
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment