A command-line tool to check email addresses and passwords against the Have I Been Pwned breach database.
Checkpwn is a command-line tool that checks email addresses and passwords against the Have I Been Pwned (HIBP) database to determine if they have been exposed in known data breaches. It helps users identify compromised credentials and prompts them to change passwords when necessary. The tool supports batch processing and secure API key management for automated security checks.
Security-conscious individuals, system administrators, and developers who want to automate breach detection for email accounts and passwords as part of their security practices.
Checkpwn offers a fast, scriptable alternative to manual HIBP website checks, with support for batch operations and local configuration. Its Rust-based implementation ensures performance and reliability for regular security audits.
Check Have I Been Pwned and see if it's time for you to change passwords.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports processing multiple accounts from .ls files, enabling automation of bulk checks without manual web browsing, as shown in the README's example commands.
Stores the HIBP API key in a local checkpwn.yml configuration file, reducing exposure risks compared to hardcoding in scripts, with a dedicated 'register' command for setup.
Available via Cargo for Rust users and Homebrew for macOS/Linux, ensuring easy installation across different operating systems without complex dependencies.
Checks both the HIBP 'paste' and 'account' databases for email addresses, providing a thorough assessment of exposure beyond basic account checks.
Users must manually register an API key via the command line before making any account API calls, adding an upfront setup step that can be cumbersome for automation.
Only accepts batch files with the .ls extension, which is non-standard and may require converting from common formats like CSV or JSON, limiting flexibility.
The README does not mention handling HIBP API rate limits, which could lead to failed requests during high-volume or automated checks without user intervention.