[Snyk] Fix for 1 vulnerabilities

[hashim21223445]

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

Snyk changed the following file(s):

• package.json
• package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Regular Expression Denial of Service (ReDoS) SNYK-JS-DIFF-14917201	708

---

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:

🦉 Regular Expression Denial of Service (ReDoS)

[semanticdiff-com]

Review changes with  

Changed Files

File	Status
package.json	41% smaller
package-lock.json	Unsupported file format

[gemini-code-assist]

Summary of Changes

Hello @hashim21223445, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, aims to enhance the project's security posture by resolving a critical Regular Expression Denial of Service (ReDoS) vulnerability. The fix involves upgrading specific npm dependencies to their latest secure versions, ensuring the application is protected against this known exploit.

Highlights

• Vulnerability Fix: This pull request addresses a Regular Expression Denial of Service (ReDoS) vulnerability (SNYK-JS-DIFF-14917201) which has a medium severity score of 708.
• Dependency Upgrades: To resolve the identified vulnerability, the next-mdx-remote dependency has been upgraded from version ^4.1.0 to ^5.0.0, and remark-gfm has been upgraded from ^3.0.1 to ^4.0.0.
• Automated Security Patch: This pull request was automatically generated by Snyk to apply the necessary security fixes and update the project's dependencies.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[mergify]

🧪 CI Insights

Here's what we observed from your CI run for 4af3dfc.

🟢 All jobs passed!

But CI Insights is watching 👀

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, updates next-mdx-remote and remark-gfm to fix a ReDoS vulnerability. While addressing the security issue is important, both updates are major version bumps and introduce significant breaking changes that are not addressed in this PR.

The upgrade of next-mdx-remote to v5.0.0 changes the API of the serialize function, which will cause your application to break. I've left a comment with details on how to adapt your code.

Additionally, the upgrade of remark-gfm to v4.0.0 may be incompatible with the version of remark used by next-mdx-remote, potentially causing build or runtime issues.

Please review the comments and apply the necessary code changes to ensure the application remains functional after these dependency upgrades.

[gemini-code-assist]

Upgrading next-mdx-remote to v5.0.0 is a major version bump with breaking changes that will break the application. The serialize function from next-mdx-remote/serialize has changed, and the scope option has been removed. The project uses this option in utils/mdx-utils.js in the getPostBySlug function.

To fix this, you need to update utils/mdx-utils.js to let serialize handle frontmatter parsing automatically. Without this fix, the application will fail at build time or runtime.

Here's an example of how to update getPostBySlug:

// utils/mdx-utils.js

export const getPostBySlug = async (slug) => {
  const postFilePath = path.join(POSTS_PATH, `${slug}.mdx`);
  const source = fs.readFileSync(postFilePath);

  const mdxSource = await serialize(source, {
    parseFrontmatter: true,
    mdxOptions: {
      remarkPlugins: [remarkGfm],
      rehypePlugins: [rehypePrism],
    },
  });

  return { mdxSource, data: mdxSource.frontmatter, postFilePath };
};

This change removes the need for manual parsing with gray-matter in this function.

[gemini-code-assist]

Upgrading remark-gfm to v4.0.0 may cause incompatibility issues. This version is intended for remark v15, but next-mdx-remote v5 and its underlying MDX v2 dependencies are typically built for remark v14.

This version mismatch could lead to peer dependency warnings or runtime errors.

Please verify compatibility. If issues arise, you may need to revert remark-gfm to ^3.0.1. The security vulnerability might be resolved by the next-mdx-remote upgrade alone, as it could update the underlying vulnerable dependency. You can check this by running npm ls diff after installing with only the next-mdx-remote upgrade.