Danicar5551/pqc-check

This is a nascent security scanning tool with zero adoption signals (0 stars, 0 forks, 14 days old). The core idea—detecting legacy crypto patterns to prepare for PQC standards—is sound and timely, but the execution appears to be a straightforward pattern-matching linter. No evidence of novel detection heuristics, integration with vulnerability databases, or domain-specific PQC guidance. The project lacks community traction, documentation depth, or production hardening. Frontier risk is medium because (1) major security vendors (GitHub, GitLab, Snyk) already offer or will offer similar scanning as standard platform features, and (2) NIST's PQC standardization creates incentive for large players to bundle migration tooling into broader DevSecOps platforms. However, the niche is specialized enough that a well-executed, highly opinionated tool could survive if it targets specific languages/frameworks and provides clear PQC migration paths. Current state: indistinguishable from a freshman security project; would require significant differentiation (e.g., automated refactoring suggestions, integration with NIST standards, specific-language depth) to reach defensibility 5+.