A Python script that generates graphs and charts from password cracking results (hashcat/john potfiles) for security analysis.
Graphcat is a Python script that generates graphs and charts from password cracking results, specifically from hashcat and John the Ripper potfiles. It helps security analysts visualize cracking statistics, password patterns, and strength metrics to assess credential security and inform defensive strategies.
Security professionals, penetration testers, and red teamers who conduct password cracking assessments and need to analyze and report on the results.
It automates the visualization of cracking data into ready-to-use charts and PDF reports, saving time over manual analysis and providing clear insights into password vulnerabilities and cracking effectiveness.
Generate graphs and charts based on password cracking result
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Installation is straightforward with 'git clone' and 'pip install .', and it runs via simple command-line arguments with a helper flag (-h) for quick reference, as shown in the README.
It accepts hash files in three formats (hash-only, username:hash, and secretsdump), including handling password history data for similarity analysis, providing flexibility for different cracking outputs.
The tool automatically produces a comprehensive PDF report with charts like cracked vs. uncracked hashes and password length distribution, saving manual effort in data visualization.
It works with both hashcat and John the Ripper potfiles (using the -john flag), making it versatile for common password cracking tools in security assessments.
It only supports hashcat and John the Ripper, ignoring other cracking tools, which restricts its use in diverse security setups without manual data conversion.
The charts are predefined (e.g., top passwords, format repartition) with no customization options mentioned, limiting adaptability for specific reporting needs.
There is no GUI or web-based dashboard, requiring users to be comfortable with terminal commands, which may hinder less technical stakeholders.
The README lacks details on error management or debugging beyond a -debug flag, potentially leading to opaque failures with malformed input files.