gosec

actions/gosec

Fork 0

mirror of https://github.com/securego/gosec.git synced 2024-11-05 11:35:51 +00:00

Commit graph

Author	SHA1	Message	Date
Ville Skyttä	f1f0056a90	Spelling fixes (#717 )	2021-11-09 21:02:24 +01:00
Cosmin Cojocar	92b3644625	Fix error parsing when the loaded package is empty Signed-off-by: Cosmin Cojocar <cosmin.cojocar@gmx.ch>	2019-05-01 08:52:23 +02:00
Martin Vrachev	62b5195dd9	Report for Golang errors (#284 ) * 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>	2019-02-27 08:24:06 +10:00

Author

SHA1

Message

Date

Ville Skyttä

f1f0056a90

Spelling fixes (#717 )

2021-11-09 21:02:24 +01:00

Cosmin Cojocar

92b3644625

Fix error parsing when the loaded package is empty

Signed-off-by: Cosmin Cojocar <cosmin.cojocar@gmx.ch>

2019-05-01 08:52:23 +02:00

Martin Vrachev

62b5195dd9

Report for Golang errors (#284 )

* 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>

2019-02-27 08:24:06 +10:00

3 commits