Skip to content

[Snyk] Fix for 2 vulnerabilities - #13251

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

[Snyk] Fix for 2 vulnerabilities#13251
sestinj wants to merge 1 commit into
mainfrom
snyk-fix-acc95b982468bb201f8cd01d18c52e72

Conversation

@sestinj

@sestinj sestinj commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

snyk-top-banner

Snyk has created this PR to fix 2 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 Heap-based Buffer Overflow
SNYK-JS-SHARP-19653587
  731  
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 requested a review from a team as a code owner September 11, 2026 10:34
@sestinj

sestinj commented Sep 11, 2026

Copy link
Copy Markdown
Contributor Author

Merge Risk: High

This release includes a high-risk major version upgrade for @c15t/react and a medium-risk minor version upgrade for sharp.

@c15t/react from 1.8.5 to 2.0.0 (High Risk)

This is a major version upgrade with significant breaking changes requiring a manual migration. The update introduces a completely new styling system, a rewritten backend, and numerous API changes.

Key Breaking Changes:

  • Styling System Overhaul: The legacy styling system (v1) and CSS-in-JS approach have been removed. You must migrate to the new token-based styling system and import CSS stylesheets directly.
  • API and Configuration Changes: Provider options have been flattened, the /show-consent-banner API is replaced by /init, and several properties like gdprTypes have been renamed.
  • Backend v1 Removed: The previous backend and its /v1 routes are no longer available.
  • License Change: The package license has changed from GPL-3.0 to Apache-2.0.

Recommendation: A migration is required. The maintainers have provided a CLI tool (@c15t/cli) with codemods to assist with the upgrade from v1 to v2. It is strongly advised to perform this upgrade in a separate, dedicated effort.

sharp from 0.34.5 to 0.35.4 (Medium Risk)

This upgrade crosses a minor version boundary (0.34.x to 0.35.x) and introduces breaking changes, primarily related to the environment and installation process.

Key Changes:

  • Node.js Version Requirement: Support for Node.js 18 has been dropped. This version now requires Node.js >= 20.9.0.
  • Installation Script Removed: To enhance security, the install script has been removed. This may impact build and deployment pipelines that relied on the previous installation behavior.
  • API Removals and Renames: Several deprecated properties and methods have been removed, such as failOnError and paletteBitDepth. The format.jp2k has been renamed to format.jp2.

Recommendation: Verify that your environment meets the new Node.js version requirement. Review your build and deployment processes to ensure they are compatible with the removal of the installation script. Check your codebase for any usage of the removed or renamed APIs.

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

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