[Snyk] Security upgrade scrapy from 1.2.0 to 2.11.2

[matiskay]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • requirements.txt

⚠️ Warning

Scrapy 2.9.0 requires cryptography, which is not installed.
Scrapy 2.9.0 has requirement lxml>=4.3.0, but you have lxml 3.6.4.
Scrapy 2.9.0 has requirement zope.interface>=5.1.0, but you have zope.interface 4.3.2.
Scrapy 2.9.0 has requirement parsel>=1.5.0, but you have parsel 1.0.3.
Scrapy 2.9.0 has requirement w3lib>=1.17.0, but you have w3lib 1.15.0.
Scrapy 2.9.0 has requirement pyOpenSSL>=21.0.0, but you have pyOpenSSL 16.1.0.
Scrapy 2.9.0 has requirement Twisted>=18.9.0, but you have Twisted 16.4.1.
Scrapy 2.9.0 has requirement service-identity>=18.1.0, but you have service-identity 16.0.0.
pyOpenSSL 16.1.0 requires cryptography, which is not installed.
Mako 1.0.4 requires MarkupSafe, which is not installed.
itemloaders 1.1.0 has requirement parsel>=1.5.0, but you have parsel 1.0.3.
itemloaders 1.1.0 has requirement w3lib>=1.17.0, but you have w3lib 1.15.0.

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	581/1000 Why? Recently disclosed, Has a fix available, CVSS 5.9	Exposure of Sensitive Information to an Unauthorized Actor SNYK-PYTHON-SCRAPY-6841708	scrapy: 1.2.0 -> 2.11.2	No	No Known Exploit
	611/1000 Why? Recently disclosed, Has a fix available, CVSS 6.5	Files or Directories Accessible to External Parties SNYK-PYTHON-SCRAPY-6841836	scrapy: 1.2.0 -> 2.11.2	No	No Known Exploit
	501/1000 Why? Recently disclosed, Has a fix available, CVSS 4.3	URL Redirection to Untrusted Site ('Open Redirect') SNYK-PYTHON-SCRAPY-6841882	scrapy: 1.2.0 -> 2.11.2	No	No Known Exploit

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

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.

Check the changes in this PR to ensure they won't cause issues with your project.

---

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

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 URL Redirection to Untrusted Site ('Open Redirect')