SWI-3723 [Snyk] Security upgrade @nestjs/common from 6.11.11 to 9.0.0

[bwappsec]

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

Snyk changed the following file(s):

• samples/client/petstore/typescript-nestjs-v6-provided-in-root/builds/default/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Unintended Proxy or Intermediary ('Confused Deputy') SNYK-JS-AXIOS-15965856	247
	HTTP Response Splitting SNYK-JS-AXIOS-15969258	184
	Improper Removal of Sensitive Information Before Storage or Transfer SNYK-JS-FOLLOWREDIRECTS-16032162	50

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.

[bwappsec]

This is a major upgrade across three versions (v6 → v9) of NestJS and introduces significant breaking changes that require code and environment modifications.

Key Breaking Changes:

• HttpModule and HttpService Moved: In NestJS v9, HttpModule and HttpService have been moved from @nestjs/common to the new @nestjs/axios package. You must update your imports and add @nestjs/axios as a project dependency.

• Node.js Version Requirement: Support for older Node.js versions is dropped. NestJS v7 requires Node.js >= 10.13.0, and v9 will require a more recent version (likely Node.js 12 or 14 at a minimum). You must ensure your runtime environment is updated.

• Stricter Provider Validation: NestJS v9 enforces stricter rules for custom providers. For example, using the inject property with useClass is no longer permitted and will cause an error. These providers must be refactored, likely to use useFactory.

• Ecosystem-wide Updates: Upgrading @nestjs/common will necessitate upgrading all other @nestjs/* packages (e.g., @nestjs/core, @nestjs/testing) to corresponding major versions to ensure compatibility.

Recommendation: This upgrade cannot be done automatically. A staged migration is recommended: first upgrade to the latest v7, then to v8, and finally to v9, addressing the breaking changes at each step. Thoroughly test your application after each major version increment.

Source: NestJS Migration Guides, Community discussions

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	Scan Engine	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.