# E-LINT-010: file the checks cannot read

The security checks read every Go file of an app, so an app is made of plain Go files that are built on every machine. A folder of the app holds a source file in another language, such as assembly (`.s`), C (`.c`, `.h`) or a compiled object (`.syso`), which the go command would build into the app unread; or a Go file that no package of the app compiles on this machine: one with a `//go:build` line that leaves it out of this build, one whose name ends in an operating system or a processor other than this machine's, such as `_windows.go` or `_arm64.go` on Linux on amd64, or one that imports `"C"`, since the checks load the app with cgo off. A `//go:build` line that this build meets, such as `//go:build linux || darwin` on Linux, passes. Such a file could be built on another machine without being checked. A Go file in a folder that an `ignore` directive of `go.mod` names is refused too, since `./...` leaves that folder out and the checks do not read it. Test files (`_test.go`), files whose names start with `.` or `_`, `testdata` folders, folders whose names start with `.` or `_`, and folders that hold another module are not read; a package of the app in a `testdata` folder, in a folder whose name starts with `.` or `_`, or in a folder that `go.mod` ignores may not be imported either (E-LINT-001).

**Fix:** delete the file, or make it a plain Go file with no `//go:build` line or `_<os>` or `_<arch>` name suffix that leaves it out of this build and no `import "C"`, in a folder that `go.mod` does not ignore.
