20250401 ak.improve testability

[aqk]

WIP

[socket-security[bot]]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​walletconnect/​types@​2.18.0 ⏵ 2.19.0	+1		+1
	@​walletconnect/​utils@​2.18.0 ⏵ 2.19.0
	@​types/​react-dom@​18.3.1 ⏵ 19.0.4			-1
	@​types/​jest@​27.5.2 ⏵ 29.5.14	+1
	@​walletconnect/​sign-client@​2.18.0 ⏵ 2.19.0
	@​types/​react@​18.3.12 ⏵ 19.0.10	+1		+1
	@​types/​node@​16.18.120 ⏵ 22.13.9			+1
	@​emotion/​styled@​11.13.5 ⏵ 11.14.0
	react@​18.3.1 ⏵ 19.0.0	+1
	@​emotion/​react@​11.13.5 ⏵ 11.14.0
	@​testing-library/​user-event@​13.5.0 ⏵ 14.6.1
	express@​4.21.1 ⏵ 4.21.2
	@​mui/​material@​6.1.8 ⏵ 6.4.6	+1		+1
	typescript@​5.8.2
	@​testing-library/​react@​16.0.1 ⏵ 16.2.0	+1
	react-dom@​18.3.1 ⏵ 19.0.0	+1		+1
	styled-components@​6.1.13 ⏵ 6.1.15				+3
	ts-jest@​29.2.5 ⏵ 29.2.6			+1
	web-vitals@​2.1.4 ⏵ 4.2.4	+1		+1

View full report

[socket-security[bot]]

[!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		[email protected] has a License Policy Violation. License: CC-BY-4.0 (package/ThirdPartyNoticeText.txt) License: MIT-Khronos-old (package/ThirdPartyNoticeText.txt) From: resources/gaming-fe/package-lock.json → npm/[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/[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.

View full report