Skip to content

[Snyk] Fix for 2 vulnerabilities - #104

Open
OBPeteS wants to merge 1 commit into
masterfrom
snyk-fix-fba265fd99dc32ca7c8733688b76c6ea
Open

[Snyk] Fix for 2 vulnerabilities#104
OBPeteS wants to merge 1 commit into
masterfrom
snyk-fix-fba265fd99dc32ca7c8733688b76c6ea

Conversation

@OBPeteS

@OBPeteS OBPeteS commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

snyk-top-banner

Snyk has created this PR to fix 2 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

  • package.json
  • yarn.lock

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.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Allocation of Resources Without Limits or Throttling
SNYK-JS-BRACEEXPANSION-18313044
  828  
high severity Inefficient Algorithmic Complexity
SNYK-JS-JSYAML-18313070
  828  

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

@OBPeteS

OBPeteS commented Jul 27, 2026

Copy link
Copy Markdown
Contributor Author

Merge Risk: High

This update includes major version jumps for remark-cli and textlint, introducing significant breaking changes. Both packages have transitioned to be ESM-only and require newer versions of Node.js.

remark-cli: 7.0.1 → 11.0.0

Risk: HIGH

This is a multi-major version upgrade that transitions remark-cli and the wider remark ecosystem to be ESM-only.

Breaking Changes:

  • ESM Only: The package is now pure ESM. This requires usage within an ESM project (using "type": "module" in package.json or .mjs files) and using import instead of require().
  • Node.js Requirement: remark-cli v11 requires Node.js 16 or later.
  • Configuration: The way plugins and configurations are loaded has changed to be asynchronous to support ESM. Configuration files like .remarkrc.js may need to be updated to .remarkrc.mjs or adapted for ESM syntax.

Recommendation: This upgrade will likely require significant changes to your build process and configuration files. It is recommended to consult the remark and unified documentation on ESM usage.

textlint: 11.9.0 → 14.4.1

Risk: HIGH

This is a significant upgrade spanning three major versions (v12, v13, v14), with breaking changes in each.

Key Changes by Version:

  • v12: Dropped support for Node.js 10, requiring Node.js 12+. Modules were updated to target ES2015.
  • v13: Dropped support for Node.js 14, requiring Node.js 16+. Introduced a new, async-first API (createLinter) to support ESM-based rules and plugins. The old APIs (TextLintEngine, TextFixEngine) were deprecated. For most CLI users, there were no breaking changes, but programmatic usage was heavily impacted.
  • v14: Dropped support for Node.js 16, requiring Node.js 18.14+. The experimental --parallel flag was removed. Deprecation warnings were added for the old APIs, which are scheduled for removal in v15.

Recommendation: Verify your Node.js version is at least 18.14.0. If you are using textlint programmatically, you must migrate from the deprecated TextLintEngine and TextFixEngine APIs to the new createLinter API to ensure future compatibility.

@textlint-rule/textlint-rule-no-unmatched-pair: 1.0.7 → 1.0.8

Risk: LOW

This is a patch release. It is expected to contain bug fixes and minor improvements without any breaking changes.

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