-
Updated
Apr 13, 2021 - Rust
sast
Here are 67 public repositories matching this topic...
-
Updated
Apr 3, 2021 - CSS
- terrascan version: 1.2
- Operating System: all
Description
When scanning a repo, if the severity field is not all caps (HIGH|MEDIUM|LOW), when violations are output, the color of the severity field does not show up. The compare should be case-insensitive, OR we can normalize the severity field.
What I Did
terrascan scan -d [dir]
-
Updated
Apr 16, 2021 - Go
It will be a fun exercise to make scan work for mono repos such as https://github.com/swapnil-linux/spring-boot-examples
In theory, this can be achieved using a bit of bash with the new scan AppImage.
-
Updated
Apr 4, 2021 - C++
-
Updated
Jan 26, 2021 - Go
-
Updated
Apr 11, 2021 - Python
-
Updated
Apr 3, 2021 - JavaScript
Scan the docker network for open ports and vulnerable services.
-
Updated
Sep 4, 2020 - Python
-
Updated
Mar 21, 2021 - JavaScript
-
Updated
Apr 3, 2021 - Python
-
Updated
Apr 14, 2021 - HTML
-
Updated
Apr 16, 2021 - Python
-
Updated
Apr 13, 2021 - JavaScript
-
Updated
Apr 13, 2019 - Java
-
Updated
Mar 10, 2021 - TypeScript
-
Updated
Mar 29, 2021
-
Updated
Dec 9, 2020
-
Updated
Mar 10, 2021 - TypeScript
-
Updated
Apr 1, 2021 - TypeScript
-
Updated
Feb 24, 2021 - Shell
Improve this page
Add a description, image, and links to the sast topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the sast topic, visit your repo's landing page and select "manage topics."
Describe the bug
According to the SARIF spec,
invocationshould be the child of arun:https://docs.oasis-open.org/sarif/sarif/v2.1.0/csprd01/sarif-v2.1.0-csprd01.html#_Toc10540933
Currently
build_sarif_outputis nesting it at the root of the document, which is producing SARIF which does not conform to the specification:https://github.com/returntocorp/semgrep/blob/9a73a142dc