Skip to content

[Snyk] Fix for 2 vulnerabilities #37

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
stevemac007 wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Snyk] Fix for 2 vulnerabilities #37

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions requirements.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,8 +21,8 @@ s3transfer==0.1.1
six==1.10.0
tqdm==4.11.2
Unidecode==0.4.19
Werkzeug==0.15.5
Werkzeug==3.1.5
Copy link

@amazon-q-developer amazon-q-developer bot Jan 13, 2026

Choose a reason for hiding this comment

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

🛑 Breaking Change Risk: Werkzeug upgrade from 0.15.5 to 3.1.5 is a major version jump that introduces breaking changes. This could cause runtime failures with Flask 1.0 which expects Werkzeug>=0.14 but may not be compatible with 3.x versions. The PR warning shows Flask 1.0 has requirement Werkzeug>=0.14, but you have Werkzeug 3.1.5, indicating a potential compatibility issue.

wsgi-request-logger==0.4.5
zappa==0.20.2
wheel>=0.38.0 # not directly required, pinned by Snyk to avoid a vulnerability
urllib3>=1.26.5 # not directly required, pinned by Snyk to avoid a vulnerability
urllib3>=2.6.3 # not directly required, pinned by Snyk to avoid a vulnerability
Copy link

@amazon-q-developer amazon-q-developer bot Jan 13, 2026

Choose a reason for hiding this comment

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

🛑 Dependency Conflict Risk: The urllib3 upgrade to >=2.6.3 combined with other outdated dependencies creates a cascade of compatibility issues. The PR warning shows multiple dependency conflicts including missing required packages (MarkupSafe for Jinja2, s3transfer version mismatch for boto3). These conflicts could cause import errors or runtime failures.