Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactor: Security upgrade graphql from 16.6.0 to 16.8.1 #8752

Closed

Conversation

parseplatformorg
Copy link
Contributor

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
    • package-lock.json

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
medium severity 658/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 5.3
Denial of Service (DoS)
SNYK-JS-GRAPHQL-5905181
No Proof of Concept

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

Commit messages
Package name: graphql The new version differs by 10 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:

🦉 Denial of Service (DoS)

@parse-github-assistant
Copy link

I will reformat the title to use the proper commit message syntax.

@parse-github-assistant parse-github-assistant bot changed the title [Snyk] Security upgrade graphql from 16.6.0 to 16.8.1 refactor: Security upgrade graphql from 16.6.0 to 16.8.1 Sep 19, 2023
@parse-github-assistant
Copy link

Thanks for opening this pull request!

  • ❌ Please link an issue that describes the reason for this pull request, otherwise your pull request will be closed. Make sure to write it as Closes: #123 in the PR description, so I can recognize it.

@codecov
Copy link

codecov bot commented Sep 19, 2023

Codecov Report

Patch coverage: 80.41% and project coverage change: -9.15% ⚠️

Comparison is base (7f89399) 94.46% compared to head (a596a57) 85.32%.
Report is 38 commits behind head on alpha.

❗ Current head a596a57 differs from pull request most recent head 9144a2d. Consider uploading reports for the commit 9144a2d to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##            alpha    #8752      +/-   ##
==========================================
- Coverage   94.46%   85.32%   -9.15%     
==========================================
  Files         185      186       +1     
  Lines       14647    14770     +123     
==========================================
- Hits        13837    12602    -1235     
- Misses        810     2168    +1358     
Files Changed Coverage Δ
src/Adapters/Cache/RedisCacheAdapter.js 16.00% <0.00%> (-75.31%) ⬇️
src/Controllers/DatabaseController.js 93.82% <ø> (-0.17%) ⬇️
src/Options/Definitions.js 100.00% <ø> (ø)
src/Options/index.js 100.00% <ø> (ø)
src/RestWrite.js 94.73% <ø> (-0.30%) ⬇️
src/index.js 100.00% <ø> (ø)
src/triggers.js 95.35% <ø> (ø)
src/cli/utils/runner.js 52.17% <40.00%> (-34.19%) ⬇️
src/Adapters/Auth/mfa.js 81.73% <81.73%> (ø)
src/Adapters/Auth/AuthAdapter.js 36.36% <100.00%> (+6.36%) ⬆️
... and 6 more

... and 11 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@mtrezza mtrezza closed this Sep 21, 2023
@mtrezza mtrezza deleted the snyk-fix-372a8d0469f6aeeeb009882ee86331d5 branch January 3, 2024 00:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants