Skip to content

Conversation

@mandibles232
Copy link

snyk-top-banner

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

Snyk changed the following file(s):

  • requirements.txt

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:

🦉 Deserialization of Untrusted Data

@mandibles232 mandibles232 requested a review from a team as a code owner December 25, 2025 00:00
@mandibles232
Copy link
Author

Merge Risk: High

The upgrade of langchain-core from 0.1.53 to 0.3.81 is high risk, while the marshmallow upgrade is medium risk.

  • langchain-core (0.1.53 → 0.3.81): High Risk

    • This upgrade forces a migration from Pydantic v1 to v2 and drops support for Python 3.8. Pydantic v2 has significant API differences from v1, which will require code changes for any projects using Pydantic models with LangChain.
  • marshmallow (3.22.0 → 3.26.2): Medium Risk

    • This upgrade drops support for Python 3.8. It also introduces a breaking change where custom validators must raise a ValidationError instead of returning False.

Recommendation: Prioritize addressing the langchain-core upgrade. The mandatory migration to Pydantic v2 requires careful code review and refactoring before this change can be merged.

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.

3 participants