Skip to content

Conversation

@snyk-bot
Copy link

Snyk has created this PR to upgrade @metalsmith/markdown from 1.4.0 to 1.5.0.

merge advice
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.
  • The recommended version was released 21 days ago, on 2022-03-20.

The recommended version fixes:

Severity Issue PriorityScore (*) Exploit Maturity
Regular Expression Denial of Service (ReDoS)
SNYK-JS-MARKED-2342082
586/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 5.3
Proof of Concept
Regular Expression Denial of Service (ReDoS)
SNYK-JS-MARKED-2342073
586/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 5.3
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Release notes
Package name: @metalsmith/markdown
  • 1.5.0 - 2022-03-20
    • feat: update marked@2.1.0 to marked@4.0.12 #57
    • feat: Update debug to ^4.3.4 3b6b861
    • feat: export named plugin b9aaa0f
  • 1.4.0 - 2021-12-12
    • Bump lodash from 4.17.15 to 4.17.21 e67efeb
    • Bump glob-parent from 5.1.0 to 5.1.2 808fd6c
    • Aligned dotfiles & default repository files with core metalsmith plugins 0f1cc8f
    • Dropped support for Node <8. Documented 'keys' option in README. Updated dev dependencies baf3422
    • Add LICENSE file 411e94c
    • Updated marked to 2.1.0, debug to 4.3.3 149d3d6
    • Fixes marked incorrect node compat + jsdocs cfb384e
    • Fixes security vulnerabilities 2c899a7
from @metalsmith/markdown GitHub release notes
Commit messages
Package name: @metalsmith/markdown

Compare


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

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