Release changes to master

[prashantasdeveloper]

JIRA Link

Insert JIRA url here

Changelog / Description

Add description in points. Use bulleting/numbering to list the changes/features.

Checklist -

• New Feature ?
• Updated swagger annotation (if API structure is changed) ?
• Unit Test (if possible) ?
• Updated the Readme.md (if required) ?

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​nestjs/​schematics@​11.0.9 ⏵ 11.1.0			+1
	eslint@​8.48.0 ⏵ 8.57.1
	@​polymeshassociation/​signing-manager-types@​3.4.2 ⏵ 3.7.1	+1		+1	+4
	eslint-config-prettier@​9.0.0 ⏵ 9.1.2	+1		+1
	@​commitlint/​cli@​20.1.0 ⏵ 20.5.3	+1		+1
	@​polymeshassociation/​hashicorp-vault-signing-manager@​3.5.0 ⏵ 4.1.0	+1		+2	+10
	@​polymeshassociation/​local-signing-manager@​3.5.2 ⏵ 4.1.1	-2			+8
	@​polymeshassociation/​fireblocks-signing-manager@​2.5.0 ⏵ 3.0.0	+3		+2	+9
	@​types/​lodash@​4.14.198 ⏵ 4.17.24
	@​types/​node@​18.17.14 ⏵ 18.19.130
	typeorm@​0.3.27 ⏵ 0.3.30	-16	+2	+1
	@​polymeshassociation/​polymesh-sdk@​29.1.0-beta.9 ⏵ 30.0.0	-3		+1	-1
	eslint-plugin-promise@​6.1.1 ⏵ 6.6.0
	eslint-plugin-import@​2.28.1 ⏵ 2.32.0
	class-validator@​0.14.0 ⏵ 0.14.4	+1		+1
	rhea-promise@​3.0.1 ⏵ 3.0.3				+3
	@​nestjs/​schedule@​6.0.1 ⏵ 6.1.3	+1		+1
	@​nestjs/​typeorm@​11.0.0 ⏵ 11.0.2	+1		+1
	@​nestjs/​cli@​11.0.10 ⏵ 11.0.23	+1		+1
	@​nestjs/​config@​4.0.2 ⏵ 4.0.4
	@​nestjs/​swagger@​11.2.1 ⏵ 11.4.4	+1		+1
	path-to-regexp@​8.3.0 ⏵ 8.4.2	+1	+18	+1
	pg@​8.16.3 ⏵ 8.21.0	+1		+1
	eslint-plugin-prettier@​5.0.0 ⏵ 5.5.6	+1
	@​polymeshassociation/​polymesh-types@​6.2.0 ⏵ 7.4.0	+1		+24	+5
	@​nestjs/​common@​11.1.8 ⏵ 11.1.27	+1
	@​nestjs/​core@​11.1.8 ⏵ 11.1.27	+6	+2
	@​nestjs/​testing@​11.1.8 ⏵ 11.1.27	+1			+1
	eslint-plugin-n@​16.0.2 ⏵ 16.6.2				+4
	@​nestjs/​platform-express@​11.1.8 ⏵ 11.1.27	+1
	@​commitlint/​config-conventional@​20.0.0 ⏵ 20.5.3

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 "▶" to expand/collapse)
Warn		Obfuscated code: npm @polkadot/keyring is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/@polymeshassociation/signing-manager-types@3.7.1 → npm/@polymeshassociation/hashicorp-vault-signing-manager@4.1.0 → npm/@polymeshassociation/local-signing-manager@4.1.1 → npm/@polymeshassociation/polymesh-types@7.4.0 → npm/@polymeshassociation/polymesh-sdk@30.0.0 → npm/@polymeshassociation/fireblocks-signing-manager@3.0.0 → npm/@polkadot/keyring@13.5.9 ℹ Read more on: This package | This alert | What is obfuscated code? 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 support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@polkadot/keyring@13.5.9. 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		Obfuscated code: npm es-abstract is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/eslint-plugin-import@2.32.0 → npm/es-abstract@1.24.2 ℹ Read more on: This package | This alert | What is obfuscated code? 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 support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/es-abstract@1.24.2. 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		Obfuscated code: npm execa is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/@semantic-release/exec@7.1.0 → npm/@semantic-release/npm@12.0.2 → npm/semantic-release@24.2.9 → npm/execa@9.6.1 ℹ Read more on: This package | This alert | What is obfuscated code? 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 support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/execa@9.6.1. 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		Obfuscated code: npm js-yaml is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/@commitlint/cli@20.5.3 → npm/@nestjs/cli@11.0.23 → npm/eslint@8.57.1 → npm/semantic-release@24.2.9 → npm/js-yaml@4.2.0 ℹ Read more on: This package | This alert | What is obfuscated code? 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 support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/js-yaml@4.2.0. 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		Obfuscated code: npm npm is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/@semantic-release/npm@12.0.2 → npm/npm@10.9.8 ℹ Read more on: This package | This alert | What is obfuscated code? 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 support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/npm@10.9.8. 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		Obfuscated code: npm npm is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/@semantic-release/npm@12.0.2 → npm/npm@10.9.8 ℹ Read more on: This package | This alert | What is obfuscated code? 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 support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/npm@10.9.8. 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		Obfuscated code: npm strtok3 is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/@nestjs/common@11.1.27 → npm/strtok3@10.3.5 ℹ Read more on: This package | This alert | What is obfuscated code? 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 support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/strtok3@10.3.5. 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		Obfuscated code: npm ts-api-utils is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/@typescript-eslint/parser@6.9.1 → npm/@typescript-eslint/eslint-plugin@6.9.1 → npm/ts-api-utils@1.4.3 ℹ Read more on: This package | This alert | What is obfuscated code? 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 support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/ts-api-utils@1.4.3. 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		Obfuscated code: npm typeorm is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package.json → npm/typeorm@0.3.30 ℹ Read more on: This package | This alert | What is obfuscated code? 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 support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/typeorm@0.3.30. 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		Obfuscated code: npm typeorm is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package.json → npm/typeorm@0.3.30 ℹ Read more on: This package | This alert | What is obfuscated code? 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 support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/typeorm@0.3.30. 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		Obfuscated code: npm validator is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/class-validator@0.14.4 → npm/validator@13.15.35 ℹ Read more on: This package | This alert | What is obfuscated code? 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 support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/validator@13.15.35. 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		Obfuscated code: npm webpack is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/@nestjs/cli@11.0.23 → npm/ts-loader@9.5.4 → npm/webpack@5.106.2 ℹ Read more on: This package | This alert | What is obfuscated code? 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 support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/webpack@5.106.2. 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.

View full report

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
2 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube Cloud