From af3ba73daf8465b0194b5bf67498aeea542dcf1c Mon Sep 17 00:00:00 2001
From: Philip Helger <philip@helger.com>
Date: Fri, 7 Nov 2025 13:10:45 +0100
Subject: [PATCH 1/2] Updated API code snippet in readme for GitHub #117

---
 README.md | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/README.md b/README.md
index e87dedb..a363a7d 100644
--- a/README.md
+++ b/README.md
@@ -74,12 +74,12 @@ The [CLI documentation](./docs/cli.md) shows further configuration options.
 The Validator can also be used in own Java Applications via the API. An example use of the API as follows:
 
 ```java
-Path scenarios = Paths.get("scenarios.xml");
-Configuration config = Configuration.load(scenarios.toUri());
-Input document = InputFactory.read(testDocument);
-
+URL scenarios = this.getClass().getClassLoader().getResource("scenarios.xml");
+Configuration config = Configuration.load(scenarios.toURI()).build(ProcessorProvider.getProcessor());
 Check validator = new DefaultCheck(config);
-Result validationResult = validator.checkInput(document);
+
+Input document = InputFactory.read(testDocument);
+Result report = validator.checkInput(document);
 
 // examine the result here
 ```
@@ -139,8 +139,8 @@ To use the standalone version with Maven coordinates, add the respective classif
 
 This section describes the next steps planned in the Validator development.
 
-* Release version 1.6.0 based on Java 11 and using Jakarta 4.x. - Autumn 2025
-    * Drop support of version 1.5.x when version 1.6 is released
+* Version 1.5.x is frozen - no maintainance, no support
+* Version 1.6.x - no feature development, but maintainance and best-effort support
 * Develop version 2.0.0 which will include major API incompatibilities - Winter 2025 
     * Rework scenarios.xml
     * Rework report output engine

From 28e85d3942c466108a9435560ee0ba356571651f Mon Sep 17 00:00:00 2001
From: Renzo Kottmann <renzo.kottmann@finanzen.bremen.de>
Date: Fri, 7 Nov 2025 15:04:48 +0100
Subject: [PATCH 2/2] Upgrade mvn owasp dep check to 12.1.8

---
 pom.xml | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/pom.xml b/pom.xml
index 7269c73..5d04818 100644
--- a/pom.xml
+++ b/pom.xml
@@ -46,7 +46,7 @@
         <version.jaxb-impl>4.0.5</version.jaxb-impl>
         <version.lombok>1.18.42</version.lombok>
         <version.mockito>4.11.0</version.mockito>
-        <version.owasp-dependency-check>10.0.4</version.owasp-dependency-check>
+        <version.owasp-dependency-check>12.1.8</version.owasp-dependency-check>
         <version.rest-assured>5.5.5</version.rest-assured>
         <version.saxon-he>12.8</version.saxon-he>
         <version.slf4j>2.0.17</version.slf4j>
@@ -239,7 +239,8 @@
                         <configuration>
                             <rules>
                                 <requireMavenVersion>
-                                    <version>[3.3.9,)</version>
+                                    <!-- minimum for OWASP check-->
+                                    <version>[3.6.3,)</version>
                                 </requireMavenVersion>
                                 <requireJavaVersion>
                                     <!-- Required for "-proc:full" required for Lombok: 
@@ -617,6 +618,10 @@
                         <artifactId>dependency-check-maven</artifactId>
                         <version>${version.owasp-dependency-check}</version>
                         <configuration>
+                        <!-- Specifies if the build should be failed if a CVSS score 
+                        above a specified level is identified. 
+                        The default is 11 which means since the CVSS scores are 0-10, 
+                        by default the build will never fail.-->
                             <failBuildOnCVSS>0</failBuildOnCVSS>
                             <suppressionFiles>
                                 <suppressionFile>${project.basedir}/owasp-suppressions.xml</suppressionFile>