scieloorg / opac-airflow

Componente de coleta e identificação das alterações realizadas nos metadados do SciELO
BSD 2-Clause "Simplified" License
3 stars 11 forks source link

[Snyk] Fix for 3 vulnerabilities #456

Open rondinelisaad opened 1 month ago

rondinelisaad commented 1 month ago

snyk-top-banner

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

Snyk changed the following file(s):

⚠️ Warning ``` marshmallow-sqlalchemy 0.29.0 has requirement marshmallow>=3.0.0, but you have marshmallow 2.21.0. Flask-AppBuilder 2.3.4 requires Flask-JWT-Extended, which is not installed. Flask-AppBuilder 2.3.4 requires Flask-Login, which is not installed. Flask-AppBuilder 2.3.4 has requirement email-validator<2,>=1.0.5, but you have email-validator 2.1.0. cattrs 1.10.0 has requirement attrs>=20, but you have attrs 19.3.0. botocore 1.33.13 has requirement urllib3<1.27,>=1.25.4; python_version < "3.10", but you have urllib3 2.0.7. argcomplete 1.12.3 has requirement importlib-metadata<5,>=0.23; python_version == "3.7", but you have importlib-metadata 6.7.0. apache-airflow 1.10.12 requires flask-swagger, which is not installed. apache-airflow 1.10.12 requires json-merge-patch, which is not installed. apache-airflow 1.10.12 requires flask-admin, which is not installed. apache-airflow 1.10.12 requires python-slugify, which is not installed. apache-airflow 1.10.12 requires future, which is not installed. apache-airflow 1.10.12 requires unicodecsv, which is not installed. apache-airflow 1.10.12 requires flask-login, which is not installed. apache-airflow 1.10.12 requires python-nvd3, which is not installed. apache-airflow 1.10.12 requires thrift, which is not installed. apache-airflow 1.10.12 has requirement jinja2<2.12.0,>=2.10.1, but you have jinja2 3.1.4. ```

[!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:

🦉 Cross-site Scripting (XSS) 🦉 Regular Expression Denial of Service (ReDoS)