We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug @anandtiwarics Gitlab SAST scans parser seems outdated. UI of archerysec is displaying vulnerability name as "Not Found" although vuln name has got a real name. Maybe this parser is outdated ? archerysec/scanners/scanner_parser/staticscanner_parser/gitlab_sast_json_report_parser.py
Line 62 in 643a598
name = "Not Found"
There is no message any more on recent scan reports
message
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
@anandtiwarics Gitlab SAST scans parser seems outdated.
UI of archerysec is displaying vulnerability name as "Not Found" although vuln name has got a real name.
Maybe this parser is outdated ?
archerysec/scanners/scanner_parser/staticscanner_parser/gitlab_sast_json_report_parser.py
Line 62 in 643a598
There is no
message
any more on recent scan reportsTo Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: