Bump to @metamask/eslint-config-* v15

[mcmire]

Fix lint violations from the upgrade.

Also bump typescript-eslint to 8.48.1.

Changes for @metamask/eslint-config-* packages:

• https://github.com/MetaMask/eslint-config/blob/main/packages/base/CHANGELOG.md
• https://github.com/MetaMask/eslint-config/blob/main/packages/nodejs/CHANGELOG.md
• https://github.com/MetaMask/eslint-config/blob/main/packages/typescript/CHANGELOG.md
• https://github.com/MetaMask/eslint-config/blob/main/packages/vitest/CHANGELOG.md

---

Note

Upgrades MetaMask ESLint configs to v15 and typescript-eslint 8.48.1, with minor ESLint and Yarn config adjustments.

• Tooling:
  • Dev deps: Bump @metamask/eslint-config* to ^15.0.0 and typescript-eslint to ^8.48.1.
  • ESLint config (eslint.config.mjs): Remove parserOptions.project, keep tsconfigRootDir; no other rule changes.
  • Yarn constraints (yarn.config.cjs): Add Yarn typedef alias and JSDoc for constraints args.

^{Written by Cursor Bugbot for commit 63fbdfc. This will update automatically on new commits. Configure here.}

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​metamask/​eslint-config-vitest@​1.0.0 ⏵ 15.0.0	+3		+2	+6
	typescript-eslint@​8.12.2 ⏵ 8.48.1			-1
	@​typescript-eslint/​utils@​8.26.0 ⏵ 8.48.1			+1
	@​metamask/​eslint-config@​14.0.0 ⏵ 15.0.0			+1	+10
	@​metamask/​eslint-config-nodejs@​14.0.0 ⏵ 15.0.0	+1			+8
	@​metamask/​eslint-config-typescript@​14.0.0 ⏵ 15.0.0	+1		+2	+8

View full report

[socket-security]

Warning

MetaMask internal reviewing guidelines:

• Do not ignore-all
• Each alert has instructions on how to review if you don't know what it means. If lost, ask your Security Liaison or the supply-chain group
• Copy-paste ignore lines for specific packages or a group of one kind with a note on what research you did to deem it safe.
  @SocketSecurity ignore npm/PACKAGE@VERSION

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Potential code anomaly (AI signal): npm ignore is 100.0% likely to have a medium risk anomaly Notes: The code fragment represents a conventional, well-structured path-ignore utility with caching and recursive parent-directory evaluation. Windows path normalization is present for compatibility but does not indicate malicious intent. No indicators of data leakage, external communication, or covert backdoors were found. Security impact primarily revolves around correct ignore semantics rather than intrinsic vulnerabilities. The component remains appropriate for use in a broader security-conscious pipeline if used with careful awareness of what is being ignored. Confidence: 1.00 Severity: 0.60 From: ? → npm/typescript-eslint@8.48.1 → npm/ignore@7.0.5 ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/ignore@7.0.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.

Ignoring alerts on:

• @typescript-eslint/typescript-estree@8.48.1
• @typescript-eslint/utils@8.48.1

View full report

[mcmire]

@SocketSecurity ignore npm/@typescript-eslint/typescript-estree@8.48.1

I have searched the codebase and am not finding where this fetch is happening 🤔

[Gudahtt]

That alert is a false positive - I asked the Socket team about it recently

[Gudahtt]

LGTM!

[Gudahtt]

@SocketSecurity ignore npm/@typescript-eslint/utils@8.48.1

This is another known false positive that I investigated elsewhere

[cryptodev-2s]

LGTM!