Add PQC Migration Readiness to Code Analysis

[Arpan0995]

Suggestion type

• Project
• Resource

Adds PQC Migration Readiness under Code Analysis in README_SOURCE.md.

It is a static analyzer for Java source that finds quantum-vulnerable cryptography (RSA, ECDSA and (EC)DH through the JCA) and scores how hard each site is to migrate, including code typed against concrete key classes such as RSAPublicKey. It runs on source alone, with no build or classpath, and ships as a CLI, a Maven plugin on Maven Central and a GitHub Action, with Markdown, JSON and SARIF output. Apache-2.0.

Checklist

• I searched the list and existing issues for duplicates.
• I changed README_SOURCE.md, not the generated README.md.
• This pull request contains one suggestion.
• The suggestion is relevant to Java or the JVM and fits its chosen category.
• I used the canonical project or resource link.
• The suggestion is current and maintained.
• The concise, neutral description explains its distinguishing value and ends with punctuation.
• Licensing is clear and any restrictive terms are disclosed where applicable.

Disclosure: I maintain this project.

---

Summary by cubic

Adds PQC Migration Readiness to the Code Analysis list in README_SOURCE.md.

The tool is a static analyzer that scans Java source for quantum-vulnerable JCA usage (RSA, ECDSA, (EC)DH) and ranks each site by how hard it is to migrate to post-quantum cryptography, running on source alone with no build or classpath required.

^{Written for commit 4fe6cc3. Summary will update on new commits.}

[cubic-dev-ai]

No issues found across 1 file

_{Re-trigger cubic}