-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
✨ Fortify: Support .fpr format #9590
Conversation
Contextual Security AnalysisAs DryRun Security performs checks, we’ll summarize them here. You can always dive into the detailed results in the section below for checks.
Chat with your AI-powered Security Buddy by typing Install and configure more repositories at DryRun Security |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
great work, happy to see such a fast reaction time, added some comments for improvement
Co-authored-by: Steve Lohr <[email protected]>
Co-authored-by: Steve Lohr <[email protected]>
Please review again @schdief |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, thanks again
as written, maybe we can enrich the test metadata too, to give more context about the scan, which is especially imprtant if there are no findings at all, to verify that the scan itself was valid (not just empty files scanned etc.)
what is the release cadence for defectdojo? when can we use this after merging?
https://documentation.defectdojo.com/contributing/branching-model/ |
see issue #9584