OpenAPI Generator 7.25.0

Last reviewed Oct 28, 2026

Export as PDF

Prompt Details

Prompt Composition

2prompts
  1. Java 25113 lines · 2.8K tokens
  2. OpenAPI Generator 7.25.061 lines · 3.3K tokens
Total174 lines · 6.1K tokens

CWE Coverage

  • 15
  • 20
  • 22
  • 59
  • 78
  • 79
  • 88
  • 89
  • 94
  • 95
  • 117
  • 190
  • 201
  • 208
  • 209
  • 214
  • 295
  • 297
  • 323
  • 327
  • 338
  • 347
  • 362
  • 367
  • 378
  • 427
  • 459
  • 470
  • 471
  • 488
  • 494
  • 502
  • 532
  • 611
  • 653
  • 674
  • 681
  • 732
  • 770
  • 772
  • 776
  • 789
  • 807
  • 862
  • 863
  • 915
  • 916
  • 918
  • 922
  • 942
  • 1333

Prompt Preview

Apply the Java 25 prompt first for Java 25 deployments. OpenAPI Generator 7.25.0 itself requires Java 11 or later; the generated application's runtime and framework requirements depend on the selected generator and library. Apply the client and server rules below only to the named output targets.

Runtime and specification trust

  • Pin the generator JAR or the Maven or Gradle plugin version in the build files or lock file, pin any container image by digest, and pin wrappers separately; look up the current generator release before writing a version. Verify the effective generator with version; an npm wrapper version does not identify the downloaded Java generator version.
  • Select generatorName, library, and serialization options explicitly and inspect config-help -g <generator> --full-details --feature-set from the same generator version the build runs. Check the generated dependency declarations and target JDK; OpenAPI 3.1 support is beta and feature support varies by generator.
  • Review the specification, descriptions, examples, defaults, operation IDs, schema names, server URLs, and vendor extensions as build inputs capable of influencing generated code. Accept only the intended operations and features; successful parsing does not establish that these inputs are safe to compile or publish.
  • Keep specification validation enabled: omit --skip-validate-spec, keep plugin skipValidateSpec=false, and keep Gradle validateSpec=true. Fail on validation errors and validate the same reviewed input used for generation; these checks do not enforce runtime request