Skip to content

[Snyk] Security upgrade gatsby-remark-mermaid from 2.1.0 to 3.0.0 #16

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

DevenGengan
Copy link
Owner

snyk-top-banner

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

Snyk changed the following file(s):

  • docs/package.json
  • docs/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
critical severity Prototype Pollution
SNYK-JS-DOMPURIFY-8318045
  751  

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:

🦉 Prototype Pollution

Copy link

dryrunsecurity bot commented Nov 4, 2024

DryRun Security Summary

The provided code change updates the version of the gatsby-remark-mermaid package from 2.1.0 to 3.0.0 in the package.json file, which is generally a positive change that should be reviewed and thoroughly tested to ensure compatibility and security.

Expand for full summary

Summary:

The code change in the provided package.json file is updating the version of the gatsby-remark-mermaid package from 2.1.0 to 3.0.0. From an application security perspective, this update is generally a positive change, as it likely includes bug fixes, security improvements, and new features. However, it's important to review the changelog or release notes for the new version to ensure there are no known security vulnerabilities or breaking changes that could impact the application. Additionally, it's a good practice to thoroughly test the application after upgrading any dependencies to ensure that the new version of the gatsby-remark-mermaid package is compatible with the rest of the application and does not introduce any regressions or security issues. Overall, the code change appears to be a routine update to a dependency, and there is nothing immediately concerning from an application security perspective.

Files Changed:

  • docs/package.json: This file has been updated to use version 3.0.0 of the gatsby-remark-mermaid package, which is an upgrade from the previous version 2.1.0.

Code Analysis

We ran 9 analyzers against 2 files and 1 analyzer had findings. 8 analyzers had no findings.

Analyzer Findings
Sensitive Files Analyzer 1 finding

Riskiness

🟢 Risk threshold not exceeded.

View PR in the DryRun Dashboard.

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.

2 participants