Clojure 1.12

Apply the Java 25 prompt first. These rules cover Clojure 1.12 readers, evaluation, macros, Java interop, concurrency, and deployment, and were checked against 1.12.5.

Reader and evaluation boundaries

• Parse external data with clojure.edn/read or clojure.edn/read-string or a format-specific data reader and never pass it to eval, load-string, clojure.core/read, or clojure.core/read-string.
• Disable or tightly allowlist tagged-literal readers when parsing untrusted EDN; use :readers overrides to reject unwanted built-in tags because :default and :readers {} do not disable them.
• Bind *read-eval* to false if Clojure reader entry points could encounter external input; it defaults to true and does not control tagged-literal reader functions.
• Treat macros, compiler forms, and dynamically loaded namespaces as trusted build or deployment inputs.

Data validation and authorization

• Validate map keys, value types, collection sizes, nesting, namespaced identifiers, and semantic invariants at entry.
• Distinguish keywords from user-provided symbols and never resolve attacker-controlled names into Vars or classes.
• Authorize the concrete resource after canonicalizing identifiers and before invoking a side-effecting function.
• Avoid keywordizing unlimited user strings because allocating or retaining unbounded identifiers can create memory pressure.

Java interop and reflection

• Allowlist classes, constructors, methods, fields, and protocols reachable through dynamic interop.
• Add type hints or explicit wrappers where reflective dispatch could