mirror of
https://github.com/securego/gosec.git
synced 2024-12-28 21:08:22 +02:00
62b5195dd9
* Report for Golang errors Right now if you use Gosec to scan invalid go file and if you report the result in a text, JSON, CSV or another file format you will always receive 0 issues. The reason for that is that Gosec can't parse the AST of invalid go files and thus will not report anything. The real problem here is that the user will never know about the issue if he generates the output in a file. Signed-off-by: Martin Vrachev <mvrachev@vmware.com>
35 lines
691 B
Go
35 lines
691 B
Go
package gosec
|
|
|
|
import (
|
|
"sort"
|
|
)
|
|
|
|
// Error is used when there are golang errors while parsing the AST
|
|
type Error struct {
|
|
Line int `json:"line"`
|
|
Column int `json:"column"`
|
|
Err string `json:"error"`
|
|
}
|
|
|
|
// NewError creates Error object
|
|
func NewError(line, column int, err string) *Error {
|
|
return &Error{
|
|
Line: line,
|
|
Column: column,
|
|
Err: err,
|
|
}
|
|
}
|
|
|
|
// sortErros sorts the golang erros by line
|
|
func sortErrors(allErrors map[string][]Error) {
|
|
|
|
for _, errors := range allErrors {
|
|
sort.Slice(errors, func(i, j int) bool {
|
|
if errors[i].Line == errors[j].Line {
|
|
return errors[i].Column <= errors[j].Column
|
|
}
|
|
return errors[i].Line < errors[j].Line
|
|
})
|
|
}
|
|
}
|