Run pqc-scan in CI to fail a pull request if it introduces quantum-vulnerable cryptography like RSA.
Generate a Cryptography Bill of Materials report to inventory an organization's cryptographic usage.
Scan only files changed in a git diff for a fast pre-merge cryptography check.
| sachhg/pqc-scan | 0-bingwu-0/live-interpreter | 010zx00x1/faresnipe | |
|---|---|---|---|
| Stars | 2 | 2 | 2 |
| Language | Python | Python | Python |
| Setup difficulty | easy | moderate | easy |
| Complexity | 3/5 | 2/5 | 2/5 |
| Audience | developer | general | general |
Figures from each repo's GitHub metadata at analysis time.
Requires Python 3.10 or later, installs via pip with all scanning dependencies bundled.
pqc-scan is a command-line tool that scans your code, config files, and dependencies for cryptography that would be broken by a future quantum computer, before it becomes a real problem. It parses your actual source code using a proper code-structure parser rather than fragile text patterns, so it can point to the exact line that is vulnerable, explain why, and suggest a specific replacement algorithm that has been standardized by the US National Institute of Standards and Technology, known as NIST. The README explains the underlying risk in plain terms: most of the public-key cryptography that secures the internet today, including RSA and elliptic-curve algorithms, would be broken by a quantum algorithm called Shor's algorithm if a powerful enough quantum computer existed. Symmetric encryption like AES and hashing like SHA-256 are only weakened, not broken, and remain considered safe. The README also warns about a tactic called harvest now, decrypt later, where someone captures encrypted data today with the plan to decrypt it once quantum computers are capable enough, which puts any long-lived sensitive data at risk right now, not just in the future. The tool is installed from source using pip and requires Python 3.10 or later. All the parsing libraries it depends on install automatically, with no separate compiler or toolchain needed. It runs as a command called pqc-scan with four subcommands: scan, which checks a folder or file and prints a report to the console or to formats like SARIF or JSON, report, which writes a machine-readable file such as a Cryptography Bill of Materials, init, which creates a starter configuration file, and rules, which lists every detection rule the tool knows about. Common options let a user filter results by severity, scan only files changed in the current git diff for faster pull request checks, exclude certain folders, and fail with a nonzero exit code when problems are found, which makes it usable as an automated check in a GitHub Actions pipeline.
A command-line and CI scanner that finds cryptography in your code that would be broken by future quantum computers, and suggests NIST-approved replacements.
Mainly Python. The stack also includes Python, Tree-sitter, GitHub Actions.
License terms are not stated in the README excerpt.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
double-check against the repo, no cap.