A secure, cross-platform Git credential helper that provides authentication to GitHub, Azure DevOps, Bitbucket, and GitLab.
Git Credential Manager (GCM) is a secure Git credential helper that provides authentication to popular Git hosting services like GitHub, Azure DevOps, Bitbucket, and GitLab. It solves the problem of managing Git credentials securely across different platforms, offering features like multi-factor authentication and secure storage. It replaces older platform-specific credential managers and works seamlessly with Git's existing workflow.
Developers and teams using Git with cloud-based or on-premises Git hosting services who need secure, cross-platform credential management with support for multi-factor authentication.
Developers choose GCM because it provides a consistent, secure authentication experience across Windows, macOS, and Linux, with built-in support for multi-factor authentication and secure credential storage, eliminating the need for platform-specific solutions.
Secure, cross-platform Git credential storage with authentication to GitHub, Azure Repos, and other popular Git hosting services.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Provides installers for Windows, macOS, and Linux, ensuring a uniform authentication experience across all major operating systems, as highlighted in the README's cross-platform support feature.
Enables two-factor or multi-factor auth for Azure DevOps, GitHub, Bitbucket, and GitLab, offering enhanced security over Git's built-in credential helpers that only handle username/password.
Utilizes platform-specific secure mechanisms like Windows Credential Manager or macOS Keychain to store credentials safely, as noted in the README's secure credential storage feature.
Called implicitly by Git during operations like `git push`, automatically opening authentication windows when needed, reducing manual configuration and user effort.
Does not support SSH remotes; users must manage SSH keys separately, which can be inconvenient for teams standardized on SSH, as admitted in the README's current status section.
Requires the .NET runtime to be installed, adding overhead and potential compatibility issues, especially on lightweight or non-standard Linux distributions.
Incompatible with Git 1.x and Git 2.26.2, forcing upgrades or workarounds for older systems, as specified in the supported Git versions section.