[Snyk] Security upgrade eslint from 8.18.0 to 9.0.0

[tirthbodawala]

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• package.json
• package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Prototype Pollution SNYK-JS-JSYAML-13961110	631

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Prototype Pollution

[chatgpt-codex-connector]

💡 Codex Review

pawjs/package-lock.json

Lines 3394 to 3418 in 77ccb6d

	"node_modules/@typescript-eslint/eslint-plugin": {
	"version": "5.29.0",
	"resolved": "https://registry.npmjs.org/@typescript-eslint/eslint-plugin/-/eslint-plugin-5.29.0.tgz",
	"integrity": "sha512-kgTsISt9pM53yRFQmLZ4npj99yGl3x3Pl7z4eA66OuTzAGC4bQB5H5fuLwPnqTKU3yyrrg4MIhjF17UYnL4c0w==",
	"dependencies": {
	"@typescript-eslint/scope-manager": "5.29.0",
	"@typescript-eslint/type-utils": "5.29.0",
	"@typescript-eslint/utils": "5.29.0",
	"debug": "^4.3.4",
	"functional-red-black-tree": "^1.0.1",
	"ignore": "^5.2.0",
	"regexpp": "^3.2.0",
	"semver": "^7.3.7",
	"tsutils": "^3.21.0"
	},
	"engines": {
	"node": "^12.22.0 || ^14.17.0 || >=16.0.0"
	},
	"funding": {
	"type": "opencollective",
	"url": "https://opencollective.com/typescript-eslint"
	},
	"peerDependencies": {
	"@typescript-eslint/parser": "^5.0.0",
	"eslint": "^6.0.0 || ^7.0.0 || ^8.0.0"

Update TypeScript ESLint packages for v9 peer dependency

The commit bumps eslint to 9.0.0, but @typescript-eslint/eslint-plugin is still pinned to 5.29.0 whose peerDependencies allow only eslint ^6 || ^7 || ^8. With npm ≥7 this unresolved peer dependency causes npm install to abort with ERESOLVE unless run with --force, and even if forced the plugin has not been validated against ESLint 9 so linting may fail. Please upgrade the @typescript-eslint/* packages to a version that supports ESLint 9 or keep ESLint at 8.x.

---

pawjs/package-lock.json

Lines 95 to 101 in 77ccb6d

	},
	"bin": {
	"paw": "paw.js",
	"pawjs": "paw.js"
	},
	"engines": {
	"node": ">=12.0"

Raise declared Node engine for ESLint 9

ESLint 9 only supports Node ≥18.18, yet the package metadata still advertises "node": ">=12.0". Users following the published engine range (or any CI pipelines pinned to Node 12/14/16) will now fail to install or execute lint tasks because the new dependency requires a newer runtime. The engine field and accompanying tooling should be updated to the minimum Node version required by ESLint 9, or the upgrade should be deferred.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".