SWI-3723 [Snyk] Security upgrade org.json4s:json4s-jackson_2.12 from 3.6.7 to 4.0.0

[bwappsec]

Snyk has created this PR to fix 1 vulnerabilities in the maven dependencies of this project.

Snyk changed the following file(s):

• samples/client/petstore/scala-akka/pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Allocation of Resources Without Limits or Throttling SNYK-JAVA-COMFASTERXMLJACKSONCORE-15365924	170	org.json4s:json4s-jackson_2.12: 3.6.7 -> 4.0.0 Major version upgrade No Path Found Proof of Concept

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Allocation of Resources Without Limits or Throttling

[bwappsec]

This is a major version upgrade from 3.x to 4.0.0. While a specific changelog for version 4.0.0 is not readily available, related project release notes confirm that this update introduces breaking binary backwards compatibility.

Potential Breaking Changes:
Based on discussions leading up to a major release, fundamental changes to the JSON Abstract Syntax Tree (AST) were planned. These likely include:

• JObject Representation: The internal structure of JObject was expected to change from JObject(List[JField]) to JObject(Map[String, JValue]). This would break any code that directly constructs, deconstructs, or pattern matches on JObject instances.
• Removal of JNothing: There were proposals to remove JNothing, which could affect code that relies on it as a 'zero' or null-equivalent value for JValue.

Recommendation:
Given the confirmation of breaking binary compatibility, this upgrade should be treated as high risk. Developers must thoroughly test all JSON parsing, serialization, and manipulation logic. Code that directly interacts with the json4s AST is especially likely to require refactoring.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

[bwappsec]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.