Skip to content
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.

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

Bump boto3 from 1.35.84 to 1.35.85 #11443

Merged
merged 1 commit into from
Dec 20, 2024

Bump boto3 from 1.35.84 to 1.35.85

219e893
Select commit
Loading
Failed to load commit list.
Merged

Bump boto3 from 1.35.84 to 1.35.85 #11443

Bump boto3 from 1.35.84 to 1.35.85
219e893
Select commit
Loading
Failed to load commit list.
DryRunSecurity / Sensitive Files Analyzer succeeded Dec 20, 2024 in 2s

DryRun Security

Details

Sensitive Files Analyzer Findings: 1 detected

⚠️ Potential Sensitive File requirements.txt (click for details)
Type Potential Sensitive File
Description It is typical for Django applications to utilize requirements.txt files to manage their dependencies. A change in this file may indicate an addition of a library/dependency which could introduce additional risk to the application either through vulnerable code, expansion of the application's attack surface via additional routes, or malicious code.
Filename requirements.txt
CodeLink
argon2-cffi==23.1.0
blackduck==1.1.3
pycurl==7.45.4 # Required for Celery Broker AWS (SQS) support
boto3==1.35.85 # Required for Celery Broker AWS (SQS) support
netaddr==1.3.0
vulners==2.2.3
fontawesomefree==6.6.0