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

[Snyk] Security upgrade json-schema-faker from 0.5.6 to 0.5.8 #1106

Merged
merged 4 commits into from
Jan 1, 2025

Conversation

pmcelhaney
Copy link
Owner

snyk-top-banner

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

Snyk changed the following file(s):

  • package.json
  • yarn.lock

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
critical severity Remote Code Execution (RCE)
SNYK-JS-JSONPATHPLUS-7945884
  786  

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:

🦉 Remote Code Execution (RCE)

Copy link

changeset-bot bot commented Nov 8, 2024

⚠️ No Changeset found

Latest commit: a025efe

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@pmcelhaney pmcelhaney enabled auto-merge January 1, 2025 20:35
@coveralls
Copy link
Collaborator

coveralls commented Jan 1, 2025

Pull Request Test Coverage Report for Build 12575364847

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 82.469%

Totals Coverage Status
Change from base Build 12575328035: 0.0%
Covered Lines: 3246
Relevant Lines: 4043

💛 - Coveralls

@pmcelhaney pmcelhaney merged commit c75f994 into main Jan 1, 2025
8 checks passed
@pmcelhaney pmcelhaney deleted the snyk-fix-9e50a5ddc14139af679471e14dcd3fe6 branch January 1, 2025 23:31
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