Node -> 18

[AprilArcus]

Update Node to version 18.

• Node 18 changes the resolution of localhost to ::1 (ipv6) instead of 127.0.0.1 (ipv4). Tell Docker to map port 5432 (postgres) on ipv6 instead of ipv4.

• Node 18 no longer spawns yarn.cmd with { shell: true } by default, so in scripts/lib/run.js, we now set it explicitly if we detect that the OS is win32.

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	next@​13.2.3
	rimraf@​4.1.2
	net@​1.0.2
	node-fetch@​2.6.7 ⏵ 3.3.2	-1
	jest@​29.4.3
	update-dotenv@​1.1.1
	lodash@​4.17.21
	tls@​0.0.1
	mock-req@​0.2.0
	nprogress@​0.2.0
	zxcvbn@​4.4.2
	passport-github2@​0.1.12
	mock-res@​0.6.0
	passport@​0.6.0
	next-with-apollo@​5.3.0
	ts-node@​10.9.1
	utf-8-validate@​6.0.3
	morgan@​1.10.0
	source-map-support@​0.5.21
	webpack@​5.94.0
	react@​18.2.0
	rc-field-form@​1.27.4
	nodemailer@​6.9.11
	nodemon@​2.0.20
	typescript@​5.0.0-dev.20230226
	pg@​8.9.0
	prettier@​2.8.4
	ts-loader@​9.4.2
	slugify@​1.6.5
	react-dom@​18.2.0
	postgraphile@​4.13.0
	redis@​4.6.5
	mjml@​4.13.0
	ts-jest@​29.0.5

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		Critical CVE: Authorization Bypass in Next.js Middleware CVE: GHSA-f82v-jwr5-mffw Authorization Bypass in Next.js Middleware (CRITICAL) Affected versions: >= 13.0.0 < 13.5.9; >= 14.0.0 < 14.2.25; >= 15.0.0 < 15.2.3; >= 12.0.0 < 12.3.5 Patched version: 13.5.9 From: @app/client/package.json → npm/next@13.2.3 ℹ Read more on: This package | This alert | What is a critical CVE? 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: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/next@13.2.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 zxcvbn is 98.0% likely obfuscated Confidence: 0.98 Location: Package overview From: @app/lib/package.json → npm/zxcvbn@4.4.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/zxcvbn@4.4.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