Skip to content

[Snyk] Security upgrade markdown from 3.3.4 to 3.8.1#19

Open
revan-zhang wants to merge 1 commit intomasterfrom
snyk-fix-ad5461727a1de9444e520b5463adf8c8
Open

[Snyk] Security upgrade markdown from 3.3.4 to 3.8.1#19
revan-zhang wants to merge 1 commit intomasterfrom
snyk-fix-ad5461727a1de9444e520b5463adf8c8

Conversation

@revan-zhang
Copy link

@revan-zhang revan-zhang commented Mar 8, 2026

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the pip dependencies of this project.

Snyk changed the following file(s):

  • docs/requirements.txt
⚠️ Warning
Markdown 3.4.4 has requirement importlib-metadata>=4.4; python_version < "3.10", but you have importlib-metadata 4.0.1.

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.
  • Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

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:

🦉 Uncaught Exception


Open with Devin

Note

Low Risk
Low risk dependency bump limited to the docs build requirements; potential risk is minor doc rendering differences or new transitive constraints during documentation builds.

Overview
Updates the docs build dependency Markdown from 3.3.4 to 3.8.1 in docs/requirements.txt to address a reported vulnerability.

Written by Cursor Bugbot for commit bb1a5e3. This will update automatically on new commits. Configure here.

The following vulnerabilities are fixed by pinning transitive dependencies:
- https://snyk.io/vuln/SNYK-PYTHON-MARKDOWN-15428352
@socket-security
Copy link

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatedmarkdown@​3.3.4 ⏵ 3.8.1100 +1100 +2100100100

View full report

@revan-zhang
Copy link
Author

revan-zhang commented Mar 8, 2026

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues

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

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

importlib-metadata==4.0.1
Jinja2==2.11.3
Markdown==3.3.4
Markdown==3.8.1
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Incompatible pinned dependency version for importlib-metadata

High Severity

Upgrading Markdown to 3.8.1 introduces a dependency conflict. Markdown>=3.4 requires importlib-metadata>=4.4 on Python < 3.10, but importlib-metadata is pinned to 4.0.1 in the same file. This will cause pip to fail to resolve dependencies (or produce runtime errors) when building docs on Python 3.9. The importlib-metadata pin needs to be bumped to at least 4.4.

Additional Locations (1)

Fix in Cursor Fix in Web

Copy link

@devin-ai-integration devin-ai-integration bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 1 additional finding.

Open in Devin Review

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