Skip to content

[Snyk] Security upgrade hugo-extended from 0.148.2 to 0.153.0#8

Open
Dustin4444 wants to merge 1 commit intomasterfrom
snyk-fix-a0956417443445a80c28dd30948a8b2d
Open

[Snyk] Security upgrade hugo-extended from 0.148.2 to 0.153.0#8
Dustin4444 wants to merge 1 commit intomasterfrom
snyk-fix-a0956417443445a80c28dd30948a8b2d

Conversation

@Dustin4444
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

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.

⚠️ Warning
Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
medium severity Arbitrary File Write via Archive Extraction (Zip Slip)
SNYK-JS-DECOMPRESSTAR-559095
  152  

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

@coderabbitai
Copy link

coderabbitai bot commented Dec 24, 2025

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch snyk-fix-a0956417443445a80c28dd30948a8b2d

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@gemini-code-assist
Copy link

Summary of Changes

Hello @Dustin4444, I'm Gemini Code Assist1! 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 bolster the project's security by upgrading the hugo-extended dependency. This upgrade specifically targets and remediates a known 'Zip Slip' vulnerability, ensuring the project's integrity against potential file system exploits. Reviewers should note the requirement for a manual yarn.lock update for zero-install environments to fully integrate these security enhancements.

Highlights

  • Security Vulnerability Fix: This pull request addresses a critical 'Arbitrary File Write via Archive Extraction (Zip Slip)' vulnerability (SNYK-JS-DECOMPRESSTAR-559095) found in the decompress-tar dependency.
  • Dependency Upgrade: The hugo-extended package has been upgraded from version 0.148.2 to 0.153.0 to resolve the identified security issue.
  • Manual yarn.lock Update Required: For users leveraging Yarn's zero-installs feature, a manual update of the .yarn/cache directory by running yarn is necessary, as yarn.lock was not automatically updated by Snyk.

🧠 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.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This PR from Snyk correctly upgrades hugo-extended to fix a security vulnerability. Before merging, please remember to run yarn install to update the yarn.lock file and commit the result, as Snyk was unable to do so. I've also added a suggestion to use a more specific version range for hugo-extended to improve future stability.

"eslint-plugin-jsx-a11y": "^6.10.2",
"globals": "^15.14.0",
"hugo-extended": ">=0.101.0",
"hugo-extended": ">=0.153.0",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

For better dependency stability, it's recommended to use a caret ^ for versioning instead of >=. Using ^0.153.0 will prevent automatic updates to future minor or major versions of hugo-extended that might introduce breaking changes, while still allowing patch updates. This helps ensure a more predictable and stable build process.

Suggested change
"hugo-extended": ">=0.153.0",
"hugo-extended": "^0.153.0",

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