Moderne OnlyThis recipe is proprietary to Moderne and runs on the Moderne platform or CLI — it isn’t part of the open-source catalog. Available with a Moderne subscription.Contact Sales

Build post-quantum TLS readiness inventory

Recipe IDio.moderne.cryptography.pqc.BuildPqcReadinessInventory

Artifactio.moderne.recipe:rewrite-cryptography

The single discovery entry point for post-quantum TLS readiness. Answers the three questions that decide whether a connection can negotiate a hybrid ML-KEM key exchange: does the module run on a runtime that offers one (JDK 27, or BouncyCastle 1.81 and later), can it still negotiate TLS 1.3 at all, and does it pin its key-exchange groups to classical curves. Changes nothing; every finding lands in one of four data tables.

Composite recipeOpenRewriteModerne Proprietary License

Try in PlatformTry this recipe in the Moderne platform. Not a user yet? You’ll get a no-setup demo environment, with nothing to install or configure.

Definition

Recipes5

• Post-quantum TLS readiness report
• Find TLS protocol configuration
• Find TLS protocol configuration in properties and YAML
• Find TLS key exchange (named groups) configuration
• Find hardcoded SSL/TLS protocol choices

Usage

Run this recipe

This recipe has no required configuration options. Users of Moderne can run it via the Moderne CLI.

You will need to have configured the Moderne CLI on your machine before you can run the following command.

shell

mod run . --recipe BuildPqcReadinessInventory

If the recipe is not available locally, then you can install it using:

RELEASE resolves to the newest release and LATEST to the newest build of any kind, including snapshots. Either one lets mod config recipes upgrade pull in later versions without editing this command; a pinned version stays where you put it.

RELEASE

mod config recipes jar install io.moderne.recipe:rewrite-cryptography:RELEASE

LATEST

mod config recipes jar install io.moderne.recipe:rewrite-cryptography:LATEST

Pinned version

mod config recipes jar install io.moderne.recipe:rewrite-cryptography:0.14.12

Data tables

PQC readiness

io.moderne.cryptography.pqc.table.PqcReadinessTable

Per-module post-quantum TLS readiness derived from the resolved Maven and Gradle dependency models and the JavaVersion markers of the module's Java sources. Modules built by tools OpenRewrite does not parse (Bazel, Ant) and BouncyCastle shaded into fat jars are invisible here, so an absent row is not evidence of health.

Column	Description
Module	Module identity: the Maven groupId:artifactId of the pom, or the Gradle project name from the GradleProject marker.
JDK version	The module's bytecode/source level, the highest of source and target compatibility across the module's JavaVersion markers, or -1 when there are no Java sources or the level is unparseable (toolchain-only builds).
JDK created by	Major version of the JDK that compiled the sources, or -1 when unknown. A secondary signal: JSSE capability depends on the runtime JDK, of which the target level is only a lower bound.
JDK classification	One of jdk-native-hybrid-capable (JEP 527 hybrid key exchange in JSSE), jdk-pqc-algos-only (JEP 496/497 ML-KEM and ML-DSA providers, TLS an explicit non-goal), jdk-not-pqc, or jdk-level-unknown.
Library name	The org.bouncycastle artifactId, e.g. bctls-jdk18on. Empty when the module has no BouncyCastle. bcutil is deliberately absent: it is an internal support artifact declared with version ranges, and its whole subtree is pruned from the graph walk. Maps to AgileSec crypto.library.name.
Library version	The resolved version, so that property-, BOM-, parent- and version-catalog-declared versions all appear concrete. Empty when the module has no BouncyCastle. Maps to AgileSec crypto.library.version.
Library language	Always Java: the row inventories a JVM module — its JDK level and the BouncyCastle artifacts it resolves. Maps to AgileSec crypto.library.language.
BouncyCastle artifact line	The artifact line parsed from the artifactId: jdk18on, jdk15to18, jdk15on, jdk14, lts8on, fips, or empty. Lines carry their own version schemes: jdk15on ends at 1.70, and fips and lts8on are numbered separately from the mainline.
BouncyCastle dependency type	direct when the module declares the artifact itself, transitive when it arrives through another dependency, empty on no-BouncyCastle rows.
BouncyCastle classification	The module-level TLS bucket, repeated on every row of the module: bctls-hybrid-capable, bctls-too-old, bctls-line-eol, bctls-absent-but-bcprov-present, no-bc, bc-fips-line-needs-separate-assessment, bc-lts-line-needs-separate-assessment, or build-file-not-resolved when the module's build tool never ran so its dependencies were never resolved — a row that must not be read as no-bc. BouncyCastle managed but not consumed (a dependencyManagement pin the module never depends on) is not on the resolved graph and therefore reads as no-bc, as do vendored jars wired up with Gradle fileTree/flatDir or Maven system scope and BouncyCastle shaded into a fat jar, none of which carry coordinates.
Code snippet	The resolved coordinate org.bouncycastle:<artifactId>:<version>. Empty on no-BouncyCastle rows.
File location	The path of the module's build file relative to the repository root.
Start line	1-based line of the start of the dependency declaration, or -1 for transitive, version-catalog-indirected and no-BouncyCastle rows.
Start column	0-based column of the start of the dependency declaration, or -1 when unavailable.
Start offset	0-based character offset of the start of the dependency declaration, or -1 when unavailable.
End line	1-based line of the end of the dependency declaration, or -1 when unavailable.
End column	0-based column of the end of the dependency declaration, or -1 when unavailable.
End offset	0-based character offset of the end of the dependency declaration, or -1 when unavailable.
Repository name	The repository name from Git provenance, e.g. payment-service. Empty when unknown.
Scan source	Where the source was scanned from, derived from Git provenance, e.g. GitHub, GitLab, Local Repository.
Branch	The branch from Git provenance, e.g. main. Empty when unknown.

TLS configuration inventory

io.moderne.cryptography.pqc.table.TlsConfigurationInventoryTable

TLS protocol version and cipher suite configuration detected in Java sources and in Spring Boot .properties/.yaml files, classified by whether TLS 1.3 — and therefore JEP 527 / BouncyCastle 1.81 hybrid key exchange — remains reachable. Non-JSSE TLS stacks (Netty, OkHttp, Tomcat and Jetty server configuration, -D flags in build files and launch scripts) are out of scope, so an absent row is not evidence that a module has no legacy TLS floor.

Column	Description
Configuration surface	The API or configuration key that produced the row, e.g. SSLContext.getInstance, SSLContext.getDefault, SSLSocket.setEnabledProtocols, SSLServerSocket.setEnabledProtocols, SSLEngine.setEnabledProtocols, SSLParameters.setProtocols, SSLSocketFactory.getDefault, HttpsURLConnection, HttpClient.newHttpClient, HttpClient.Builder.build, jdk.tls.client.protocols, jdk.tls.server.protocols, https.protocols, AbstractTlsPeer.getSupportedVersions, server.ssl.enabled-protocols, server.ssl.protocol, or a cipher-suite surface: SSLSocket.setEnabledCipherSuites, SSLServerSocket.setEnabledCipherSuites, SSLEngine.setEnabledCipherSuites, SSLParameters.setCipherSuites, jdk.tls.client.cipherSuites, jdk.tls.server.cipherSuites, server.ssl.ciphers, AbstractTlsClient.getSupportedCipherSuites. The token vocabulary is shared with the enforcement table so discovery and transformation rows can be joined.
Protocol name	The protocol family the configuration applies to: TLS, or DTLS for a datagram context. Maps to AgileSec crypto.protocol.name.
Protocol versions	Comma-joined protocol version tokens exactly as written at the site, e.g. TLSv1,TLSv1.1,TLSv1.2. BouncyCastle ProtocolVersion names are translated to their JSSE spelling and downTo ranges are expanded. Empty when nothing is declared (a default-acquisition site) or the value is not statically resolvable. Maps to AgileSec crypto.protocol.version.
Protocol cipher suites	Comma-joined cipher suite names exactly as written at the site, e.g. TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256. Filled on cipher-suite configuration rows (setEnabledCipherSuites, SSLParameters.setCipherSuites, jdk.tls.client.cipherSuites, jdk.tls.server.cipherSuites, server.ssl.ciphers, AbstractTlsClient.getSupportedCipherSuites); empty on protocol-version rows. Maps to AgileSec crypto.protocol.ciphers.
Classification	One of allows-legacy (SSLv3, TLSv1 or TLSv1.1 is declared), ceiling-below-tls13 (TLS 1.3 is unreachable — a version-specific TLSv1.2 context or a protocol list that stops at TLSv1.2), ceiling-tls13 (a version-specific TLSv1.3 context: TLS 1.3 is reachable but so is everything below it), modern-floor-tls12 (TLSv1.2 and TLSv1.3, no legacy), modern-floor-tls13 (TLSv1.3 alone), ambiguous-default (TLS, SSL or Default: the floor is decided by runtime properties), no-explicit-floor (a default-acquisition site with no protocol configuration in the file), unresolved-value (the protocol or cipher expression is not statically resolvable), dtls (a datagram context, which JEP 527 explicitly excludes), ciphers-allow-tls13 (a pinned cipher list containing at least one RFC 8446 suite), or ciphers-block-tls13 (a pinned cipher list with no RFC 8446 suite, which makes TLS 1.3 unnegotiable even when the protocol floor allows it). Version-specific SSLContext.getInstance algorithm names are ceilings, never floors: on both SunJSSE and BCJSSE they enable everything up to the named version.
PQC readiness	Whether JEP 527 / BouncyCastle 1.81+ hybrid key exchange can negotiate under this configuration: blocked (TLS 1.3 is unreachable, or the endpoint is DTLS), capable (TLS 1.3 is reachable — subject to the runtime JDK being 27+ for JSSE or BouncyCastle being 1.81+ for BCJSSE), or unknown (the value is not statically resolvable). Orthogonal to legacy hygiene: a list containing both TLSv1 and TLSv1.3 is allows-legacy and capable.
Library name	The library providing the configuration surface: JSSE, BouncyCastle, JDK (system-property surface) or Spring Boot (configuration-file surface).
Library language	The language of the source the row was found in: Java, Properties or YAML.
Code snippet	The source code of the detected API usage, e.g. Cipher.getInstance("DES").
File location	The path of the source file relative to the repository root.
Start line	1-based line of the start of the API usage.
Start column	0-based column of the start of the API usage, or -1 when unavailable.
Start offset	0-based character offset of the start of the API usage, or -1 when unavailable.
End line	1-based line of the end of the API usage.
End column	0-based column of the end of the API usage, or -1 when unavailable.
End offset	0-based character offset of the end of the API usage, or -1 when unavailable.
Repository name	The repository name from Git provenance, e.g. payment-service. Empty when unknown.
Scan source	Where the source was scanned from, derived from Git provenance, e.g. GitHub, GitLab, Local Repository.
Branch	The branch from Git provenance, e.g. main. Empty when unknown.

TLS named groups inventory

io.moderne.cryptography.pqc.table.TlsNamedGroupsInventoryTable

TLS key-exchange group configuration detected in Java sources, configuration files and checked-in JVM-options values, classified by whether an ML-KEM hybrid group is offered. -D flags in shell scripts, Dockerfiles and orchestration manifests outside the scanned repository are invisible, so an absent row is not evidence that no group pin exists.

Column	Description
Classification	A — no explicit named-groups configuration, so the runtime decides: PQC-capable on JDK 27+ (JEP 527) or BouncyCastle 1.81+, not before. B — explicit configuration naming no ML-KEM hybrid group, which pins the connection to classical key exchange regardless of the runtime. C — an ML-KEM hybrid group is already configured. B-indeterminate — a configuration surface is used but its value is not statically resolvable. never-PQC — a low-level BouncyCastle client relying on AbstractTlsClient defaults, which contain no ML-KEM group at any version, so a dependency upgrade alone will never enable PQC here. modifier — a jdk.tls.disabledAlgorithms value that disables a hybrid group, silently turning a C back into a B after an upgrade.
Configuration surface	The API or configuration key that produced the row: SSLParameters.setNamedGroups, BCSSLParameters.setNamedGroups, jdk.tls.namedGroups, jdk.tls.namedGroups JVM flag, BCJSSE provider registration, AbstractTlsClient.getSupportedGroups, AbstractTlsClient defaults, jdk.tls.disabledAlgorithms, or none (provider default) for an A row. The token vocabulary is shared with the hybrid key exchange enforcement table so discovery and transformation rows can be joined.
Protocol name	Always TLS: named-group configuration selects TLS key-exchange groups. Maps to AgileSec crypto.protocol.name.
Protocol kex algorithms	The TLS named groups — the key-exchange algorithms in AgileSec terms — named at the site, comma-joined in the order they are offered, e.g. x25519,secp256r1. BouncyCastle NamedGroup constants are recorded by their simple name. Empty when nothing is named or the value is not statically resolvable. For a modifier row this lists only the hybrid groups being disabled. Maps to AgileSec crypto.protocol.kex_algorithms.
Library name	The TLS stack the surface belongs to: JSSE or BouncyCastle. jdk.tls.namedGroups rows are recorded as JSSE even though BCJSSE honours the same property, because the property is a JDK-level surface.
Library language	The language of the source the row was found in: Java, Properties or YAML.
Code snippet	The source code of the detected API usage, e.g. Cipher.getInstance("DES").
File location	The path of the source file relative to the repository root.
Start line	1-based line of the start of the API usage.
Start column	0-based column of the start of the API usage, or -1 when unavailable.
Start offset	0-based character offset of the start of the API usage, or -1 when unavailable.
End line	1-based line of the end of the API usage.
End column	0-based column of the end of the API usage, or -1 when unavailable.
End offset	0-based character offset of the end of the API usage, or -1 when unavailable.
Repository name	The repository name from Git provenance, e.g. payment-service. Empty when unknown.
Scan source	Where the source was scanned from, derived from Git provenance, e.g. GitHub, GitLab, Local Repository.
Branch	The branch from Git provenance, e.g. main. Empty when unknown.

Taint flow

org.openrewrite.analysis.java.taint.table.TaintFlowTable

Records taint flows from sources to sinks with their taint types.

Column	Description
Source file	The source file that the method call occurred in.
Source line	The line number where the taint source is located.
Source	The source code where taint originates.
Sink line	The line number where the taint sink is located.
Sink	The sink code where taint flows to.
Taint type	The taint type that matched at the sink.

Source files that had results

org.openrewrite.table.SourcesFileResults

Source files that were modified by the recipe run.

Column	Description
Source path before the run	The source path of the file before the run. null when a source file was created during the run.
Source path after the run	A recipe may modify the source path. This is the path after the run. null when a source file was deleted during the run.
Parent of the recipe that made changes	In a hierarchical recipe, the parent of the recipe that made a change. Empty if this is the root of a hierarchy or if the recipe is not hierarchical at all.
Recipe that made changes	The specific recipe that made a change.
Estimated time saving	An estimated effort that a developer to fix manually instead of using this recipe, in unit of seconds.
Cycle	The recipe cycle in which the change was made.

Source files that had search results

org.openrewrite.table.SearchResults

Search results that were found during the recipe run.

Column	Description
Source path of search result before the run	The source path of the file with the search result markers present.
Source path of search result after run the run	A recipe may modify the source path. This is the path after the run. null when a source file was deleted during the run.
Result	The trimmed printed tree of the LST element that the marker is attached to.
Description	The content of the description of the marker.
Recipe that added the search marker	The specific recipe that added the Search marker.

Source files that errored on a recipe

org.openrewrite.table.SourcesFileErrors

The details of all errors produced by a recipe run.

Column	Description
Source path	The file that failed to parse.
Recipe that made changes	The specific recipe that made a change.
Stack trace	The stack trace of the failure.

Recipe performance

org.openrewrite.table.RecipeRunStats

Statistics used in analyzing the performance of recipes.

Column	Description
The recipe	The recipe whose stats are being measured both individually and cumulatively.
Source file count	The number of source files the recipe ran over.
Source file changed count	The number of source files which were changed in the recipe run. Includes files created, deleted, and edited.
Cumulative scanning time (ns)	The total time spent across the scanning phase of this recipe.
Max scanning time (ns)	The max time scanning any one source file.
Cumulative edit time (ns)	The total time spent across the editing phase of this recipe.
Max edit time (ns)	The max time editing any one source file.