[Snyk] Fix for 1 vulnerabilities

[snyk-io-us]

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

Snyk changed the following file(s):

• app/package.json
• app/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Inefficient Algorithmic Complexity SNYK-JS-JSYAML-17900054	828

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[snyk-io-us]

This update includes multiple major version upgrades with significant breaking changes for both @nestjs/swagger and @nx/nest. Manual developer intervention is required.

@nestjs/swagger: 7.4.0 → 11.4.5

This is a high-risk upgrade spanning four major versions (v8, v9, v10, v11). Key breaking changes include:

• Node.js Version: Support for Node.js versions below 20.0.0 has been dropped. The new minimum required version is v20.
• TypeScript Version: The Swagger plugin now requires TypeScript v4.8 or higher.
• Express v5 Integration (in v11): The underlying web framework, Express, was upgraded to v5. This introduces breaking changes to route path matching. Wildcard routes like users/* must be changed to use named parameters, for example, users/*splat. Regular expressions in setGlobalPrefix are also no longer supported.
• Module Imports: Several modules have been moved. For example, HttpModule must now be imported from @nestjs/axios instead of @nestjs/common, and CacheModule is now in its own @nestjs/cache-manager package.
• Dynamic Module Resolution (in v11): The mechanism for identifying and de-duplicating dynamic modules has changed. To share a dynamic module (e.g., TypeOrmModule.forFeature(...)) across multiple modules, you must now assign it to a variable and reuse that variable.

Recommendation: Due to the number of major versions spanned, developers should consult the official migration guides for v8, v9, v10, and v11. A careful review of all route definitions, module imports, and Node.js/TypeScript versions is essential.

@nx/nest: 19.3.2 → 20.0.9

This is a high-risk upgrade due to a fundamental change in package scoping.

• Package Scope Change: The @nrwl scope is deprecated and packages are no longer published under it. All imports, package.json dependencies, and configurations must be manually updated from the @nrwl/* scope to the @nx/* scope (e.g., @nrwl/nest becomes @nx/nest).
• No Automatic Migration: Critically, there is no automatic migration provided for the scope change. This will require a manual find-and-replace across the repository.
• Generator Updates: Generators no longer derive directory names automatically and now require an explicit --directory flag.

Recommendation: The most critical action is to manually migrate all package references from @nrwl to @nx. After updating dependencies, run npx nx migrate latest to apply other available code migrations.

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

[amazon-inspector-ohio]

⏳ I'm reviewing this pull request for security vulnerabilities and code quality issues. I'll provide an update when I'm done

[snyk-io-us]

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

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

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

[amazon-inspector-ohio]

✅ I finished the code review, and didn't find any security or code quality issues.