[Snyk] Security upgrade pyopenssl from 25.3.0 to 26.0.0

[ethanolivertroy]

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

Snyk changed the following file(s):

• requirements.txt

⚠️ Warning

ank-bm25 0.2.2 requires numpy, which is not installed.
Crawl4AI 0.4.24 requires pyOpenSSL, which is not installed.
Crawl4AI 0.4.24 requires aiosqlite, which is not installed.
Crawl4AI 0.4.24 requires pydantic, which is not installed.
Crawl4AI 0.4.24 requires tf-playwright-stealth, which is not installed.
Crawl4AI 0.4.24 requires python-dotenv, which is not installed.
Crawl4AI 0.4.24 requires aiofiles, which is not installed.
Crawl4AI 0.4.24 requires numpy, which is not installed.
Crawl4AI 0.4.24 requires aiofiles, which is not installed.
Crawl4AI 0.4.24 requires pillow, which is not installed.
Crawl4AI 0.4.24 requires litellm, which is not installed.
Crawl4AI 0.4.24 has requirement playwright>=1.49.0, but you have playwright 1.35.0.

---

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

---

[Copilot]

Copilot wasn't able to review any files in this pull request.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 0bc8f940-26ad-45e6-a53a-67fb5467a6cb

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch snyk-fix-7cbe3c10a74d52c52b7082c996d007f3

📝 Coding Plan

• Generate coding plan for human review comments

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Tip

CodeRabbit can scan for known vulnerabilities in your dependencies using OSV Scanner.

OSV Scanner will automatically detect and report security vulnerabilities in your project's dependencies. No additional configuration is required.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, addresses two security vulnerabilities by upgrading the pyopenssl package to version 26.0.0. The change ensures that the project's dependencies are secure by explicitly pinning pyopenssl in requirements.txt to prevent potential exploits.

Highlights

• Security Upgrade: Upgraded the pyopenssl package from version 25.3.0 to 26.0.0 to address two identified security vulnerabilities.
• Dependency Pinning: Explicitly added pyopenssl to requirements.txt and pinned its version, even though it was not a direct requirement, to ensure the security fix is applied.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request upgrades pyopenssl to address a security vulnerability. My review includes a suggestion to pin the dependency to an exact version (==26.0.0) instead of using a greater-than-or-equal-to (>=26.0.0) constraint. Pinning to an exact version is a best practice that improves build reproducibility and prevents accidentally pulling in future releases that may contain breaking changes. I've also suggested clarifying the comment to accurately reflect that pyopenssl is a transitive dependency.

[gemini-code-assist]

For better reproducibility and to prevent accidental upgrades to potentially incompatible versions, it's recommended to pin dependencies to an exact version using == instead of >=. This ensures that the same version of the package is used across all environments.

Additionally, the comment # not directly required can be confusing since pyopenssl is a transitive dependency of crawl4ai. The suggested comment is more accurate.

pyopenssl==26.0.0 # Pinned by Snyk to fix a vulnerability in a transitive dependency

[devin-ai-integration]

✅ Devin Review: No Issues Found

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