Skip to content

[Snyk] Security upgrade appium from 1.22.3 to 2.4.0 - #36

Open
naiba4 wants to merge 1 commit into
trunkfrom
snyk-fix-e02a538fb1849085fe13a1da371ff22a
Open

[Snyk] Security upgrade appium from 1.22.3 to 2.4.0#36
naiba4 wants to merge 1 commit into
trunkfrom
snyk-fix-e02a538fb1849085fe13a1da371ff22a

Conversation

@naiba4

@naiba4 naiba4 commented Jan 4, 2024

Copy link
Copy Markdown
Owner

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
medium severity 67/1000
Why? Confidentiality impact: None, Integrity impact: None, Availability impact: Low, Scope: Unchanged, Exploit Maturity: Proof of Concept, User Interaction (UI): None, Privileges Required (PR): None, Attack Complexity: Low, Attack Vector: Network, EPSS: 0.01055, Social Trends: No, Days since published: 21, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: Medium, Package Popularity Score: 99, Impact: 2.35, Likelihood: 2.83, Score Version: V5		 Regular Expression Denial of Service (ReDoS)
SNYK-JS-AXIOS-6124857		 Yes Proof of Concept

(*) 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.

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:

🦉 Regular Expression Denial of Service (ReDoS)

@snyk-bot
fix: package.json to reduce vulnerabilities
81c449c 
The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-AXIOS-6124857
@vercel

vercel Bot commented Jan 4, 2024 •
edited
Loading

Copy link
Copy Markdown

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

Name Status Preview Comments Updated (UTC)
gutenberg ❌ Failed (Inspect) Jan 4, 2024 11:45am
gutenberg-wd9x ❌ Failed (Inspect) Jan 4, 2024 11:45am

@pull-request-quantifier-deprecated

pull-request-quantifier-deprecated Bot commented Jan 4, 2024

Copy link
Copy Markdown

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.

@openzeppelin-code

openzeppelin-code Bot commented Jan 4, 2024

Copy link
Copy Markdown

[Snyk] Security upgrade appium from 1.22.3 to 2.4.0

Generated at commit: 81c449c56728d415eb49e8f07ea8c6e35f28fa51

🚨 Report Summary

Severity Level Results
Contracts Critical
High
Medium
Low
Note
Total		 0
0
0
0
0
0
Dependencies Critical
High
Medium
Low
Note
Total		 0
0
0
0
0
0

For more details view the full report in OpenZeppelin Code Inspector

@socket-security

socket-security Bot commented Jan 4, 2024

Copy link
Copy Markdown

Updated dependencies detected. Learn more about Socket for GitHub ↗︎

Packages Version New capabilities Transitives Size Publisher
appium 1.22.3...2.4.0 shell +101/-251 239 MB jlipps

@socket-security

socket-security Bot commented Jan 4, 2024

Copy link
Copy Markdown

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Issue Package Version Note Source
Chronological version anomaly @types/lockfile 1.0.4
Chronological version anomaly @types/uuid 9.0.7
Chronological version anomaly @types/klaw 3.0.6
Chronological version anomaly @types/lodash 4.14.202
Chronological version anomaly typescript 5.2.2
Debug access appium 2.4.0
Dynamic require appium 2.4.0
Environment variable access appium 2.4.0
Shell access appium 2.4.0
Debug access ts-node 9.1.1
Dynamic require ts-node 9.1.1
Environment variable access ts-node 9.1.1
Filesystem access ts-node 9.1.1
Major refactor ts-node 9.1.1
  • Change Percentage: 59.99
  • Current Line Count: 4836
  • Previous Line Count: 5920
  • Lines Changed: 6452
Dynamic require @appium/support 4.2.0
Environment variable access @appium/support 4.2.0
Filesystem access @appium/support 4.2.0
Dynamic require @emnapi/runtime 0.44.0
Minified code @emnapi/runtime 0.44.0
No v1 @emnapi/runtime 0.44.0
Uses eval @emnapi/runtime 0.44.0
Dynamic require consola 2.15.3
Environment variable access consola 2.15.3
Filesystem access consola 2.15.3
Dynamic require make-error 1.3.6
Major refactor make-error 1.3.6
  • Change Percentage: 64.27
  • Current Line Count: 179
  • Previous Line Count: 168
  • Lines Changed: 223
Unmaintained make-error 1.3.6
  • Last Publish: 2/19/2020, 9:34:36 AM
Dynamic require sharp 0.33.1
Environment variable access sharp 0.33.1
Modified license sharp 0.33.1
No v1 sharp 0.33.1
Empty package @img/sharp-darwin-arm64 0.33.1
Modified license @img/sharp-darwin-arm64 0.33.1
No v1 @img/sharp-darwin-arm64 0.33.1
  • Location:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

Extra Small

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@naiba4 @snyk-bot