1
0
mirror of https://github.com/securego/gosec.git synced 2025-07-03 00:27:05 +02:00
Commit Graph

11 Commits

Author SHA1 Message Date
2aaa9c41d6 Comment the reason why the file can be nil when an issue is created
Change-Id: I85295a33f540255f4904e663144b959877d0c38a
Signed-off-by: Cosmin Cojocar <ccojocar@google.com>
2025-04-08 18:19:28 +02:00
700e9a9d18 Handle nil file when creating a new issue
This can occur when there is a compilation issue into the code.

Change-Id: I8b028d454d417c33edc687dcffc68c92d18091d6
Signed-off-by: Cosmin Cojocar <ccojocar@google.com>
2025-04-08 18:19:28 +02:00
a26215cf23 Migrated the rule to the analyzers folder 2024-08-30 19:35:07 +02:00
81cda2f91f Allow excluding analyzers globally (#1180)
* This change does not exclude analyzers for inline comment
* Changed the expected issues count for G103, G109 samples for test. Previously G115 has been included in the issue count
* Show analyzers IDs(G115, G602) in gosec usage help
* See #1175
2024-08-20 10:43:40 +02:00
4bf5667f66 Add a new rule to detect integer overflow on integer types conversion
Signed-off-by: Cosmin Cojocar <cosmin@cojocar.ch>
2024-05-27 13:03:01 +02:00
e02e2f6d5b Redesign and reimplement the slice out of bounds check using SSA code representation
Signed-off-by: Cosmin Cojocar <gcojocar@adobe.com>
2023-09-20 10:19:51 +02:00
1f689968ec Fix typos in comments, vars and tests 2023-05-30 08:26:41 +02:00
d6aeaad931 correct gci linter (#946)
Signed-off-by: Matthieu MOREL <matthieu.morel35@gmail.com>
2023-03-30 09:31:24 +02:00
4340efaa9a Format file 2023-02-16 09:45:28 +01:00
f850069114 Use the gosec issue in the go analysers 2023-02-16 09:45:28 +01:00
31e63276f1 Add support for Go analysis framework and SSA code representation 2023-02-16 09:45:28 +01:00