# 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

```sh
sudo av install brew:keyring
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install keyring
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:keyring
- **Package manager:** Homebrew
- **Version:** 25.7.0
- **Source summary:** Easy way to access the system keyring service from python
- **Homepage:** <https://github.com/jaraco/keyring>
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- keyring (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 25.7.0
## 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.

### Sources

- <https://github.com/jaraco/keyring>
- <https://groups.google.com/g/python-keyring/c/m62BwNm5Wc8>
- <https://keyring.readthedocs.io/en/latest>
- <https://keyring.readthedocs.io/en/latest/history.html>
- <https://pypi.org/project/keyring/>
- <https://pypi.org/project/keyrings.alt/>


## Security Notes

narrow executable package without higher-risk signals.

- **Geiger risk:** green / low
- narrow executable package without higher-risk signals


## 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

- Unix: keyringrc.cfg

## Combined YAML source

View the package source record on GitHub. [combined/keyring.yml](https://github.com/mxcl/pkgdb/blob/main/combined/keyring.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph