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 djangosaml2 from 1.9.1 to 1.9.2 #10014

Merged
merged 1 commit into from
Apr 23, 2024

Bump djangosaml2 from 1.9.1 to 1.9.2

68f4805
Select commit
Loading
Failed to load commit list.
Merged

Bump djangosaml2 from 1.9.1 to 1.9.2 #10014

Bump djangosaml2 from 1.9.1 to 1.9.2
68f4805
Select commit
Loading
Failed to load commit list.
DryRunSecurity / Sensitive Files Analyzer succeeded Apr 23, 2024 in 0s

DryRun Security

Details

Potentially Sensitive Files: 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
Code Link
django-fieldsignals==0.7.0
hyperlink==21.0.0
django-test-migrations==1.3.0
djangosaml2==1.9.2
drf-spectacular==0.27.2
drf-spectacular-sidecar==2024.4.1
django-ratelimit==4.1.0