-
-
Notifications
You must be signed in to change notification settings - Fork 614
New issue
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
Regression of '#nosec' handling #1046
Comments
This could be related to #1043 |
Same error for me.
Here's a sample:
Adding the |
@dataclouder I was able to work around this issue by breaking the setting out from the inline struct:
|
Thanks @tbailey |
Latest gosec linter has a regression in parsing "nosec" comments; see securego/gosec#1046 Signed-off-by: Sebastiaan van Stijn <[email protected]>
Latest gosec linter has a regression in parsing "nosec" comments; see securego/gosec#1046 Signed-off-by: Sebastiaan van Stijn <[email protected]>
Latest gosec linter has a regression in parsing "nosec" comments; see securego/gosec#1046 Signed-off-by: Sebastiaan van Stijn <[email protected]> (cherry picked from commit 9e1f8d6) Signed-off-by: Cory Snider <[email protected]>
Summary
//#nosec G101
does not work in =v2.18.1Steps to reproduce the behavior
Create new project
main.go
labels.go
go.mod
gosec version
Go version (output of 'go version')
Operating system / Environment
Expected behavior
Line with #nosec G101 is not reported
Actual behavior
Line is reported as issue
The text was updated successfully, but these errors were encountered: