Feat: Angular 14 Support add

[shailesh-ladumor]

No description provided.

[socket-security]

Socket Security Pull Request Report

Dependency issues detected. If you merge this pull request, you will not be alerted to the instances of these issues again.

📜 Install scripts

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Package	Script field	Source
nice-napi@1.0.2 (added)	binding.gyp	package.json via @angular-devkit/build-angular@14.2.6, piscina@3.2.0
nice-napi@1.0.2 (added)	install	package.json via @angular-devkit/build-angular@14.2.6, piscina@3.2.0
esbuild@0.15.5 (added)	postinstall	package.json via @angular-devkit/build-angular@14.2.6

🫣 Native code

Contains native code which could be a vector to obscure malicious code, and generally decrease the likelihood of reproducible or reliable installs.

Ensure that native code bindings are expected. Consumers may consider pure JS and functionally similar alternatives to avoid the challenges and risks associated with native code bindings.

Package	Location	Source
nice-napi@1.0.2 (added)	binding.gyp	package.json via @angular-devkit/build-angular@14.2.6, piscina@3.2.0

😵‍💫 Bin script confusion

This package has multiple bin scripts with the same name. This can cause non-deterministic behavior when installing or could be a sign of a supply chain attack

Consider removing one of the conflicting packages. Packages should only export bin scripts with their name

Package	Bin script	Source
esbuild@0.15.5 (added)	esbuild	package.json via @angular-devkit/build-angular@14.2.6
esbuild-wasm@0.15.5 (added)	esbuild	package.json via @angular-devkit/build-angular@14.2.6

Pull request report summary

Issue	Status
Install scripts	⚠️ 3 issues
Native code	⚠️ 1 issue
Bin script confusion	⚠️ 2 issues
Bin script shell injection	✅ 0 issues
Unresolved require	✅ 0 issues
Invalid package.json	✅ 0 issues
HTTP dependency	✅ 0 issues
Git dependency	✅ 0 issues
Potential typo squat	✅ 0 issues
Known Malware	✅ 0 issues
Telemetry	✅ 0 issues
Protestware/Troll package	✅ 0 issues

Bot Commands

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@2.4.2

• @SocketSecurity ignore nice-napi@1.0.2
• @SocketSecurity ignore esbuild@0.15.5
• @SocketSecurity ignore esbuild-wasm@0.15.5

Powered by socket.dev