-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Add NebulousLabs/glyphcheck as linter #2329
Comments
Hey, thank you for opening your first Issue ! 🙂 If you would like to contribute we have a guide for contributors. |
A liter needs to be written using the go/analysis package to be merged to |
Hello,
https://golangci-lint.run/usage/linters/#disabled-by-default-linters--e--enable Quick example: .golangci.ymllinters:
disable-all: true
enable:
- asciicheck
example.gopackage sandbox
import "fmt"
func gitһub() {
fmt.Println("Hello")
} $ golangci-lint run
foo.go:7:6: identifier "gitһub" contain non-ASCII character: U+04BB 'һ' (asciicheck)
func gitһub() {
^ |
@adamdecaf you can follow the PR #2330 |
Your feature request related to a problem? Please describe.
Homoglyph attacks are an increasing concern for source code and currently hard to detect. There are some tools available for detecting suspect UTF-8 runes.
Describe the solution you'd like.
Including support for running a homoglyph linter would be a good first step.
Describe alternatives you've considered.
There are few if any good homoglyph linters available for the Go language. Perhaps a new linter should be written.
https://github.com/search?l=Go&q=homoglyph&type=Repositories
Additional context.
https://github.com/NebulousLabs/glyphcheck
The text was updated successfully, but these errors were encountered: