Automic VaultAutomic Vault

brew

使用 Homebrew, apk, dnf, zypper 安装 git-credential-libsecret

查看 git-credential-libsecret 的安装路径、可执行文件、元数据以及面向 AI 代理工作流的安全说明。

安装

其他安装命令

macOS

Homebrew已验证 · 100%
brew install git-credential-libsecret

local Homebrew formula metadata

Linux

Alpine Linux apk已验证 · 92%
sudo apk add git-credential-libsecret

Alpine Linux edge package indexes · git-credential-libsecret · 来源: dl-cdn.alpinelinux.org

Fedora dnf已验证 · 92%
sudo dnf install git-credential-libsecret

Fedora Rawhide package metadata · git-credential-libsecret · 来源: dl.fedoraproject.org

openSUSE zypper已验证 · 92%
sudo zypper install git-credential-libsecret

openSUSE Tumbleweed package metadata · git-credential-libsecret · 来源: download.opensuse.org

概览

软件包摘要

Git helper for accessing credentials via libsecret

命令和别名

  • git-credential-libsecret

历史

项目历史与用法

git-credential-libsecret is Git's Linux Secret Service credential helper. It lets Git store and retrieve HTTPS credentials through libsecret-backed wallets such as GNOME Keyring or KDE Wallet instead of keeping long-lived credentials in plaintext files.

项目历史

The helper entered Git's contrib area in 2016. Its initial Git commit describes it as based on the earlier GNOME Keyring helper, replacing the deprecated, GNOME-specific libgnome-keyring library with libsecret and the XDG Secret Service API.

Later Git-side changes kept the helper aligned with Git's credential protocol. A 2017 change made it unlock locked secrets through the Secret Service interface, and 2023 changes added storage for password expiry and OAuth refresh-token attributes while preserving compatibility with older stored credentials.

采用历史

Git's credential-helper documentation lists git-credential-libsecret alongside macOS Keychain and Windows Credential Manager as the Linux secure persistent storage option. That placement made it part of the standard Git credential-helper ecosystem rather than a standalone password-manager integration.

Linux package managers expose it as a separate package because the helper depends on libsecret and desktop secret-service libraries that are not always part of a minimal Git build.

使用方式

Practitioners configure it through Git's `credential.helper` setting, usually in `~/.gitconfig`, `$XDG_CONFIG_HOME/git/config`, or a repository `.git/config`. After configuration, Git invokes `git credential-libsecret` through the credential-helper protocol during HTTP authentication.

Its use case is workstation Git over HTTPS: the first authentication stores a username and password, personal access token, or generated token in the desktop secret service, and later fetch, pull, and push operations retrieve it without prompting.

为什么软件包爱好者会关心

For package maintainers, git-credential-libsecret is a small but important split from the main Git package. It is tied to desktop-secret-service dependencies, so distributing it separately keeps headless or minimal Git installs lean while giving Linux desktop users OS-integrated credential storage.

It also illustrates Git's extension model: a helper in `contrib/credential` can become a distro-facing executable without changing Git's core credential protocol.

时间线

  • 2016: Git adds `contrib/credential/libsecret` as a libsecret replacement for the GNOME Keyring helper.
  • 2017: The helper learns to unlock locked Secret Service items when reading credentials.
  • 2023: The helper stores Git credential attributes such as password expiry and OAuth refresh tokens in a backwards-compatible secret format.
  • 2025: Git fixes compilation of the libsecret helper in contrib.

Related projects

  • git-credential-cache and git-credential-store are Git's built-in generic helpers; libsecret fills the Linux secure-storage role.
  • git-credential-osxkeychain and git-credential-wincred are the analogous platform-specific helpers for macOS and Windows.
  • Git Credential Manager and git-credential-oauth are related helpers that generate or manage credentials through broader authentication workflows.

安全态势

风险级别:绿色

narrow executable package without higher-risk signals.

风险分类器

绿色 风险 · 低 置信度 · appliance

原因

  • narrow executable package without higher-risk signals

信号

  • metadata:no-higher-risk-signals

安装行为

  • formula 元数据中未记录 Homebrew post-install 钩子。
  • Homebrew bottle 元数据适用于 6 个平台目标。
  • 安装时包含 3 个运行时依赖。
  • 构建元数据列出 1 个构建依赖。

建议审查

在无人值守的代理使用前,请检查该工具是否读取明文凭据、写入远程状态、发布制品或调用插件。

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
~/.gitconfig$XDG_CONFIG_HOME/git/config.git/config

可执行文件

已安装的可执行文件

命令类型暴露范围备注
git-credential-libsecretcli全局可执行文件

新鲜度

版本和新鲜度

这些信号区分页生成时间、软件包管理器活动和上游发布比较。只有存在证据 URL 和可比较版本时,才会提示版本落后。

页面生成时间2026-07-10
管理器版本2.55.0
管理器更新时间2026-06-29
本地数据OK
上游not checked
检测到的最新版本未检测到

https://git-scm.com

  • 信息Release/tag comparison is only available for GitHub repositories.https://git-scm.comnone 置信度

安装元数据

软件包元数据

软件包键brew:git-credential-libsecret
版本2.55.0
软件包管理器Homebrew
软件包管理器页面https://formulae.brew.sh/formula/git-credential-libsecret
主页https://git-scm.com
仓库https://github.com/git/git
上游文档https://git-scm.com/doc/credential-helpers
许可证GPL-2.0-or-later
源码归档https://mirrors.edge.kernel.org/pub/software/scm/git/git-2.55.0.tar.xz
最后更新2026-06-29T20:54:53Z
Pulseupdated
依赖gettext, glib, libsecret
构建依赖pkgconf
Bottle可用 (于 arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-install未定义
服务未声明

注册表事实

源数据库详情

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namegit-credential-libsecret
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

源数据库匹配

其他软件包管理器记录

匹配项来自外部软件包管理器索引,并与本地 Automic Vault 软件包链接分开显示。

apk95%

git-credential-libsecret 2.54.0-r0

libsecret-based credential helper

https://www.git-scm.com/

sudo apk add git-credential-libsecret
  • License: GPL-2.0-only
  • Architecture: x86_64
  • Source Package: git
  • 1 依赖
  • normalized package name match
  • 匹配方式:Git Credential Libsecret
Alpine Linux edge package indexes · dl-cdn.alpinelinux.org · Alpine Linux edge package indexes: git-credential-libsecret from https://dl-cdn.alpinelinux.org/alpine/edge/main/x86_64/APKINDEX.tar.gz
dnf95%

git-credential-libsecret 2.54.0-1.fc45

Git helper for accessing credentials via libsecret

https://git-scm.com/

sudo dnf install git-credential-libsecret
  • License: BSD-3-Clause AND GPL-2.0-only AND GPL-2.0-or-later AND LGPL-2.1-or-later AND MIT
  • Category: Unspecified
  • Architecture: x86_64
  • Source Package: git
  • 6 依赖
  • 1 提供
  • normalized package name match
  • 匹配方式:Git Credential Libsecret
Fedora Rawhide package metadata · dl.fedoraproject.org · Fedora Rawhide package metadata: git-credential-libsecret from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/e5ca8ce900cd68f5419e1c39ae517343100b306336cbaeb70a3c153121d95094-primary.xml.zst
zypper95%

git-credential-libsecret 2.54.0-2.1

Git credential backend using libsecret to access keyring

https://git-scm.com/

sudo zypper install git-credential-libsecret
  • License: GPL-2.0-only
  • Category: Development/Tools/Version Control
  • Architecture: x86_64
  • Source Package: git
  • 5 依赖
  • 1 提供
  • normalized package name match
  • 匹配方式:Git Credential Libsecret
openSUSE Tumbleweed package metadata · download.opensuse.org · openSUSE Tumbleweed package metadata: git-credential-libsecret from https://download.opensuse.org/tumbleweed/repo/oss/repodata/be8d3611d25469107f32075a1697e69ec57a2b850b42348a658cc671ad5ec2b50760d02c3e59524d50da9a11d5be799bdaffba2e166e8ca8858512e3c0bd665d-primary.xml.zst

来源线索

由仓库数据生成

此页面由 av-webscripts/generate-pkg-sqlite.py 生成的私有软件包 SQLite 工件提供。

使用的来源

  • 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
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment