Skip to content

[Snyk] Fix for 10 vulnerabilities - #333

Open
papicella wants to merge 1 commit into
masterfrom
snyk-fix-9af32cac9c5ff3a6578d318bef7ff381
Open

[Snyk] Fix for 10 vulnerabilities#333
papicella wants to merge 1 commit into
masterfrom
snyk-fix-9af32cac9c5ff3a6578d318bef7ff381

Conversation

@papicella

Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to fix 10 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
critical severity Access of Resource Using Incompatible Type ('Type Confusion')
SNYK-JS-HANDLEBARS-15803084
  276  
critical severity Access of Resource Using Incompatible Type ('Type Confusion')
SNYK-JS-HANDLEBARS-15803082
  254  
high severity Arbitrary Code Injection
SNYK-JS-LODASH-15869625
  183  
critical severity Access of Resource Using Incompatible Type ('Type Confusion')
SNYK-JS-HANDLEBARS-15803086
  180  
high severity Improper Check for Unusual or Exceptional Conditions
SNYK-JS-HANDLEBARS-15807042
  169  
high severity Improper Encoding or Escaping of Output
SNYK-JS-HANDLEBARS-15807040
  165  
medium severity Prototype Pollution
SNYK-JS-LODASH-15053838
  144  
low severity Prototype Pollution
SNYK-JS-HANDLEBARS-15789775
  98  
medium severity Prototype Pollution
SNYK-JS-LODASH-15869619
  88  
medium severity Time-of-check Time-of-use (TOCTOU) Race Condition
SNYK-JS-HANDLEBARS-15813000
  62  

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:

🦉 Prototype Pollution
🦉 Access of Resource Using Incompatible Type ('Type Confusion')
🦉 Improper Encoding or Escaping of Output
🦉 More lessons are available in Snyk Learn

@papicella

Copy link
Copy Markdown
Owner Author

Merge Risk: High

This set of upgrades includes a high-risk major version update for tap and several low-risk updates.

Top Impact Upgrade

tap: 11.1.5 → 18.0.0 (HIGH RISK)

This is a significant multi-version upgrade with numerous breaking changes. Version 18 represents a complete rewrite of the library in TypeScript and introduces fundamental changes to its architecture and usage.

Key Breaking Changes:

  • Node.js Support: Support for Node.js versions below 10 has been dropped. [8, 10]
  • ESM & TypeScript: The entire library was rewritten in TypeScript to provide native support for both CommonJS and ES Modules. This may require changes to test setup and configuration. [9, 14]
  • Coverage Engine: The default coverage engine has been switched from nyc to c8, which may affect coverage reporting and configuration. [14]
  • API Changes:
    • t.has() and t.match() have been separated and are now distinct methods. [8, 10]
    • Assertion synonyms have been removed (v14+). [10]
    • beforeEach/afterEach no longer accept callbacks and are assumed to be synchronous if they do not return a promise (v1.0.0 of underlying libtap). [10]

Recommendation: This upgrade will likely require significant refactoring of your test suite. Developers should carefully review the official changelogs for versions 12 through 18 to understand the full scope of changes and plan for migration. Testing must be thorough before merging.

Source: Changelog

Other Upgrades

  • snyk 1.278.1 → 1.996.0 (Low Risk): Although this is a large version jump, Snyk uses major version numbers to indicate breaking changes. [2] Since the major version remains 1, these updates consist of new features, performance improvements, and bug fixes without impacting existing automated workflows. [1, 4]
  • lodash 4.17.4 → 4.17.23 (Low Risk): This is a patch update that addresses multiple security vulnerabilities, including prototype pollution. [5, 17] No breaking API changes are included.
  • hbs 4.0.4 → 4.2.1 (Low Risk): This minor upgrade includes dependency updates and adds a new, non-breaking rename option for partials. [16]

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

@papicella

papicella commented Apr 2, 2026

Copy link
Copy Markdown
Owner Author

Snyk checks have failed. 4 issues have been found so far.

Status Scan Engine Critical High Medium Low Total (4)
Open Source Security 0 4 0 0 4 issues
Licenses 0 0 0 0 0 issues
Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@papicella

papicella commented Apr 2, 2026

Copy link
Copy Markdown
Owner Author

Snyk checks have failed. 3 issues have been found so far.

Status Scan Engine Critical High Medium Low Total (3)
Open Source Security 0 3 0 0 3 issues
Licenses 0 0 0 0 0 issues
Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

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