Skip to content

[Snyk] Fix for 3 vulnerabilities#13012

Open
sestinj wants to merge 1 commit into
mainfrom
snyk-fix-69026770775eb10d94455b03369b444c
Open

[Snyk] Fix for 3 vulnerabilities#13012
sestinj wants to merge 1 commit into
mainfrom
snyk-fix-69026770775eb10d94455b03369b444c

Conversation

@sestinj

@sestinj sestinj commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

snyk-top-banner

Snyk has created this PR to fix 3 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
high severity Integer Overflow
SNYK-JS-SHARP-18184259
  636  
high severity Heap-based Buffer Overflow
SNYK-JS-SHARP-18184418
  636  
high severity Allocation of Resources Without Limits or Throttling
SNYK-JS-OPENTELEMETRYCORE-17373280
  624  

Breaking Change Risk

Merge Risk: High

Notice: This assessment is enhanced by AI.


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:

🦉 Allocation of Resources Without Limits or Throttling
🦉 Heap-based Buffer Overflow

@sestinj

sestinj commented Jul 23, 2026

Copy link
Copy Markdown
Contributor Author

Merge Risk: High

This update involves two high-risk upgrades with significant breaking changes requiring developer action.

1. @c15t/react from 1.8.5 to 2.0.0 (HIGH RISK)

This is a major version upgrade with a complete overhaul of the styling system and other key features. Manual migration is required.

  • New Styling System: The css-in-js approach from v1.0 has been replaced with a new token-based styling system that uses CSS stylesheet imports (e.g., @c15t/react/styles.css). This requires a full refactor of how components are styled.
  • Tracking Blocker Removed: The deprecated tracking blocker is removed in v2.0. It has been replaced by a new script loader system introduced in v1.7.0.
  • New Policy System: A new policy-driven consent system using "Policy Packs" has been introduced to manage regional consent behavior.
  • License Change: The project license has changed from GPL-3.0 to Apache-2.0.

Recommendation: Do not merge this upgrade without a thorough migration. The c15t CLI provides codemods to assist with the v1 to v2 migration. Review the v2.0.0 release notes carefully.

Source: c15t v2.0.0 Changelog

2. sharp from 0.34.5 to 0.35.0 (HIGH RISK)

Although a minor version change, this release contains multiple breaking changes, including a required Node.js version update and API removals.

  • Node.js Version Requirement: Support for Node.js 18 is dropped. The new minimum required version is Node.js 20.9.0.
  • API Removals: Several deprecated features have been removed, which will cause errors if used:
    • failOnError constructor property.
    • paletteBitDepth from metadata response.
    • Deprecated properties from the sharpen operation.
  • API Renaming: The format jp2k has been renamed to jp2 for consistency.

Recommendation: Ensure your environment is running Node.js v20.9.0 or later. Review your code for usage of the removed APIs and update accordingly.

Source: sharp v0.35.0 Changelog

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

@sestinj
sestinj requested a review from a team as a code owner July 23, 2026 03:33
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