[Snyk] Security upgrade appium from 2.0.0 to 2.5.0

[naiba4]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • package.json

⚠️ Warning

Failed to update the package-lock.json, please update manually before merging.

Vulnerabilities that will be fixed

With an upgrade:

Severity	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	125/1000 Why? Confidentiality impact: None, Integrity impact: None, Availability impact: High, Scope: Unchanged, Exploit Maturity: No data, User Interaction (UI): None, Privileges Required (PR): None, Attack Complexity: Low, Attack Vector: Network, EPSS: 0.01055, Social Trends: No, Days since published: 32, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: High, Package Popularity Score: 99, Impact: 5.99, Likelihood: 2.08, Score Version: V5	Prototype Pollution SNYK-JS-AXIOS-6144788	No	No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Commit messages

Package name: appium

The new version differs by 250 commits.

• 9cc598a chore: publish
• 91320dd fix(execute-driver-plugin): update dependency webdriverio to v8.30.0
• 23dc3d5 chore(deps): update eslint-related packages to v6.21.0
• 35742f0 chore(deps): update dependency lerna to v8.1.2
• 52a6f96 fix(execute-driver-plugin): update dependency webdriverio to v8.29.7
• d064dd1 chore(deps): update dependency prettier to v3.2.5
• 7bf4d69 chore(docutils): update dependency mkdocs-git-revision-date-localized-plugin to v1.2.4
• cdc7c09 chore(docutils): update dependency mkdocs-material to v9.5.7
• 17c7a7c chore(deps): update dependency @ types/node to v20.11.16
• 3032b00 chore(deps): update dependency npm-run-all2 to v6.1.2
• 6dacb5e fix(execute-driver-plugin): update dependency webdriverio to v8.29.3
• 5a8af13 chore(deps): update dependency @ types/node to v20.11.13
• 569db83 fix(universal-xml-plugin): update dependency fast-xml-parser to v4.3.4
• 32e9191 chore(deps): update dependency npm-run-all2 to v6 (Block Editor: LinkControl: Align documentation with current behavior WordPress/gutenberg#19736)
• 21b808d chore(deps): update eslint-related packages to v6.20.0
• 83cc668 chore(deps): update dependency npm-run-all2 to v5.0.2 (Block Library: Button: Remove title attribute handling WordPress/gutenberg#19735)
• b92ab24 chore(deps): replace dependency npm-run-all with npm-run-all2 5.0.0 (Accessibility: Show open button when the sidebar is closed and tabbingg out of the content WordPress/gutenberg#19726)
• 4c7661d chore(deps): update dependency @ types/node to v20.11.10
• b14c03f chore(docutils): update dependency mkdocs-material to v9.5.6
• 0e1eb95 chore(deps): update dependency @ types/node to v20.11.9
• edb490f chore: Remove commitlint and husky (Writing Flow: fix list selection (2) WordPress/gutenberg#19724)
• 202da83 fix(images-plugin): update dependency lru-cache to v10 ([RNMobile] Add media edit icon to image block WordPress/gutenberg#19723)
• d10b4ba chore(docutils): update consola to 3.2.3 (RichText: set correct selection on split WordPress/gutenberg#19655)
• 6cd2c54 fix(doctor): update dependency appium-adb to v12.0.3 (RNMobile - Cover Block: First iteration WordPress/gutenberg#19722)

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.

---

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

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Prototype Pollution

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
gutenberg	❌ Failed (Inspect)			Feb 7, 2024 1:42am
gutenberg-wd9x	❌ Failed (Inspect)			Feb 7, 2024 1:42am

[pull-request-quantifier-deprecated]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 1

Change summary by file extension:
.json : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

[github-actions]

Warning: Type of PR label mismatch

To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.

• Type-related labels to choose from: [Type] Automated Testing, [Type] Breaking Change, [Type] Bug, [Type] Build Tooling, [Type] Code Quality, [Type] Copy, [Type] Developer Documentation, [Type] Enhancement, [Type] Experimental, [Type] Feature, [Type] New API, [Type] Task, [Type] Technical Prototype, [Type] Performance, [Type] Project Management, [Type] Regression, [Type] Security, [Type] WP Core Ticket, Backport from WordPress Core.
• Labels found: Extra Small.

Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task.

[guardrails]

⚠️ We detected 1 security issue in this pull request:

Vulnerable Libraries (1)

Severity	Details
High	pkg:npm/[email protected] (t) upgrade to: > 2.0.0

More info on how to fix Vulnerable Libraries in JavaScript.

---

👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.