update deps #118
Merged
update deps #118
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<p>This PR was automatically created by Snyk using the credentials of a
real user.</p><br /><h3>Snyk has created this PR to fix one or more
vulnerable packages in the `npm` dependencies of this project.</h3>
#### 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
:-------------------------:|-------------------------|:-------------------------|:-------------------------|:-------------------------
 | **631/1000** <br/> **Why?** Proof of Concept
exploit, Has a fix available, CVSS 6.2 | Missing Release of Resource
after Effective Lifetime
<br/>[SNYK-JS-INFLIGHT-6095116](https://snyk.io/vuln/SNYK-JS-INFLIGHT-6095116)
| Yes | Proof of Concept
(*) Note that the real score may have changed since the PR was raised.
<details>
<summary><b>Commit messages</b></summary>
</br>
<details>
<summary>Package name: <b>c8</b></summary>
The new version differs by 6 commits.</br>
<ul>
<li><a
href="https://snyk.io/redirect/github/bcoe/c8/commit/128bee23366cb35106f5e163e99ca2ab33dafba6">128bee2</a>
chore(main): release 9.0.0 (#510)</li>
<li><a
href="https://snyk.io/redirect/github/bcoe/c8/commit/8724c706ef7a21877e6dad1185f09dce11ddd0d2">8724c70</a>
chore(deps): update dependency @ types/node to v20 (#496)</li>
<li><a
href="https://snyk.io/redirect/github/bcoe/c8/commit/66705b59557ba1e48b63172e99ef4ceb34ac1711">66705b5</a>
chore(deps): update dependency typescript to v5 (#458)</li>
<li><a
href="https://snyk.io/redirect/github/bcoe/c8/commit/b46b6401274488db5b1027a78090257095ae4f72">b46b640</a>
feat(deps): update foreground-child to promise API (#512)</li>
<li><a
href="https://snyk.io/redirect/github/bcoe/c8/commit/ef672da08d8e078bf49ea73631fb46eabf8a5dae">ef672da</a>
test: fix snapshot (#511)</li>
<li><a
href="https://snyk.io/redirect/github/bcoe/c8/commit/2cdc86bd0ac67ecf0f700212dc5f8a830ff9164f">2cdc86b</a>
chore(deps): Remove rimraf (#509)</li>
</ul>
<a
href="https://snyk.io/redirect/github/bcoe/c8/compare/a13584d5be5259ebb6a00455d352c3e8b16006de...128bee23366cb35106f5e163e99ca2ab33dafba6">See
the full diff</a>
</details>
</details>
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: <img
src="https://api.segment.io/v1/pixel/track?data=eyJ3cml0ZUtleSI6InJyWmxZcEdHY2RyTHZsb0lYd0dUcVg4WkFRTnNCOUEwIiwiYW5vbnltb3VzSWQiOiI2MWMyZTAyZi05NGE1LTQ4NGEtOWQwZi1lOTc1YzExNzk3ZDUiLCJldmVudCI6IlBSIHZpZXdlZCIsInByb3BlcnRpZXMiOnsicHJJZCI6IjYxYzJlMDJmLTk0YTUtNDg0YS05ZDBmLWU5NzVjMTE3OTdkNSJ9fQ=="
width="0" height="0"/>
🧐 [View latest project
report](https://app.snyk.io/org/jlenon7/project/97097eb1-6953-4d11-a9f3-958b2ecba250?utm_source=github&utm_medium=referral&page=fix-pr)
🛠 [Adjust project
settings](https://app.snyk.io/org/jlenon7/project/97097eb1-6953-4d11-a9f3-958b2ecba250?utm_source=github&utm_medium=referral&page=fix-pr/settings)
📚 [Read more about Snyk's upgrade and patch
logic](https://support.snyk.io/hc/en-us/articles/360003891078-Snyk-patches-to-fix-vulnerabilities)
[//]: #
(snyk:metadata:{"prId":"61c2e02f-94a5-484a-9d0f-e975c11797d5","prPublicId":"61c2e02f-94a5-484a-9d0f-e975c11797d5","dependencies":[{"name":"c8","from":"8.0.1","to":"9.0.0"}],"packageManager":"npm","projectPublicId":"97097eb1-6953-4d11-a9f3-958b2ecba250","projectUrl":"https://app.snyk.io/org/jlenon7/project/97097eb1-6953-4d11-a9f3-958b2ecba250?utm_source=github&utm_medium=referral&page=fix-pr","type":"auto","patch":[],"vulns":["SNYK-JS-INFLIGHT-6095116"],"upgrade":["SNYK-JS-INFLIGHT-6095116"],"isBreakingChange":true,"env":"prod","prType":"fix","templateVariants":["updated-fix-title","priorityScore"],"priorityScoreList":[631],"remediationStrategy":"vuln"})
---
**Learn how to fix vulnerabilities with free interactive lessons:**
🦉 [Learn about vulnerability in an interactive lesson of Snyk
Learn.](https://learn.snyk.io/?loc=fix-pr)
Co-authored-by: snyk-bot <snyk-bot@snyk.io>
This pull request was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce?
Put an
xin the boxes that applyChecklist
Put an
xin the boxes that apply. You can also fill these out aftercreating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
Further comments
If this is a relatively large or complex change, kick off the discussion by
explaining why you chose the solution you did and what alternatives you
considered, etc...