chore(deps): bump @nestjs/common from 10.4.5 to 11.0.20

[dependabot]

Bumps @nestjs/common from 10.4.5 to 11.0.20.

Release notes

Sourced from @​nestjs/common's releases.

v11.0.20

What's Changed

• refactor(common): Prevent JavaScript being wrapped in eval by @​Borewit in nestjs/nest#14974

New Contributors

• @​Borewit made their first contribution in nestjs/nest#14974

Full Changelog: nestjs/nest@v11.0.19...v11.0.20

v11.0.18

What's Changed

• chore(common): temporarily move file-type to regular deps nestjs/nest@d9a69a3

Full Changelog: nestjs/nest@v11.0.17...v11.0.18

v11.0.16 (2025-04-11)

• fix(common): use file-type to validate file mimetypes by @​Chathula in nestjs/nest#14881

v11.0.15 (2025-04-10)

Bug fixes

• platform-fastify
  • #14935 fix(fastify): methods comparison (@​johaven)

Committers: 1

• Johan Legrand (@​johaven)

v11.0.14 (2025-04-09)

Bug fixes

• platform-fastify
  • #14511 fix(fastify): adds the non-standard http methods to the instance (@​johaven)

Committers: 1

• Johan Legrand (@​johaven)

v11.0.13 (2025-04-03)

Bug fixes

• platform-fastify
  • #14895 fix(fastify-adapter): global prefix exclusion path handling w/middleware (@​KyleLilly)
• microservices
  • #14869 fix(microservices): do not re-create client connection once get client by service name (@​mingo023)

Dependencies

• platform-express
  • #14883 fix(deps): update dependency express to v5.1.0 (@​renovate[bot])
  • #14817 fix(deps): update dependency multer to v1.4.5-lts.2 (@​renovate[bot])
• platform-fastify

... (truncated)

Commits

• d5bca88 chore(@​nestjs) publish v11.0.20 release
• 8250be8 chore: add load-esm to common deps
• 1e43fcb refactor(common): Prevent JavaScript wrapping in eval
• a6bdfd1 chore(@​nestjs) publish v11.0.19 release
• 9c29ace fix(common): remove leftovers
• 11acc59 chore(@​nestjs) publish v11.0.18 release
• d9a69a3 chore(common): temporarily move file-type to regular deps
• f8a171c chore(@​nestjs) publish v11.0.17 release
• 8a287a5 chore(common): mark file-type as optional peer dep
• b6edf9a chore(@​nestjs) publish v11.0.16 release
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​radix-ui/​react-label@​2.1.0 ⏵ 2.1.6			-3
	@​radix-ui/​react-separator@​1.1.0 ⏵ 1.1.6			-3
	@​radix-ui/​react-aspect-ratio@​1.1.0 ⏵ 1.1.6			-3	-1
	class-variance-authority@​0.7.0 ⏵ 0.7.1			+2
	@​radix-ui/​react-slot@​1.2.0 ⏵ 1.2.2			-3
	@​radix-ui/​react-avatar@​1.1.1 ⏵ 1.1.9			-3	-1
	@​radix-ui/​react-switch@​1.1.1 ⏵ 1.2.4			-3	-1
	@​radix-ui/​react-collapsible@​1.1.1 ⏵ 1.1.10			-3
	@​radix-ui/​react-tabs@​1.1.1 ⏵ 1.1.11			-3
	@​types/​express@​4.17.21 ⏵ 4.17.22
	@​radix-ui/​react-hover-card@​1.1.2 ⏵ 1.1.13			-3	-1
	@​radix-ui/​react-checkbox@​1.1.2 ⏵ 1.3.1			-2
	@​radix-ui/​react-radio-group@​1.2.1 ⏵ 1.3.6			-3	-1
	@​radix-ui/​react-dropdown-menu@​2.1.2 ⏵ 2.1.14			-3
	@​radix-ui/​react-alert-dialog@​1.1.2 ⏵ 1.1.13			-4
	@​radix-ui/​react-popover@​1.1.2 ⏵ 1.1.13			-3
See 68 more rows in the dashboard

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert (click for details)
Warn		@swagger-api/[email protected] has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → npm/[email protected] → npm/@swagger-api/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@swagger-api/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		@swagger-api/[email protected] has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → npm/[email protected] → npm/@swagger-api/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@swagger-api/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		@swagger-api/[email protected] has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → npm/[email protected] → npm/@swagger-api/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@swagger-api/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		@swagger-api/[email protected] has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → npm/[email protected] → npm/@swagger-api/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@swagger-api/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		@swagger-api/[email protected] has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → npm/@swagger-api/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@swagger-api/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		@swagger-api/[email protected] has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → npm/@swagger-api/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@swagger-api/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		@swagger-api/[email protected] has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → npm/@swagger-api/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@swagger-api/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		@swagger-api/[email protected] has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → npm/[email protected] → npm/@swagger-api/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@swagger-api/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		@swagger-api/[email protected] has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → npm/[email protected] → npm/@swagger-api/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@swagger-api/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		@swagger-api/[email protected] has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → npm/[email protected] → npm/@swagger-api/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@swagger-api/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		@swagger-api/[email protected] has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → npm/[email protected] → npm/@swagger-api/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@swagger-api/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		@swagger-api/[email protected] has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → npm/[email protected] → npm/@swagger-api/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@swagger-api/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		@swagger-api/[email protected] has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → npm/@swagger-api/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@swagger-api/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		@swagger-api/[email protected] has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → npm/[email protected] → npm/@swagger-api/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@swagger-api/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		@swagger-api/[email protected] has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → npm/[email protected] → npm/@swagger-api/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@swagger-api/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		@swagger-api/[email protected] has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → npm/@swagger-api/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@swagger-api/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		@swagger-api/[email protected] has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → npm/@swagger-api/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@swagger-api/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
See 17 more rows in the dashboard

View full report