Avoid the `unsafe` package outside vetted boundaries
Production Go code should not import the `unsafe` package, which bypasses the type system and memory safety guarantees.
#Metadata
#Why it matters
`unsafe.Pointer` lets callers reinterpret arbitrary memory, hiding undefined behaviour and creating vulnerabilities that escape Go's compiler checks.
#Remediation
Replace `unsafe.Pointer` usage with typed APIs from `reflect`, `encoding/binary`, or `cgo` boundaries that explicitly document and contain the unsafe scope.
#Repository path
The generated metadata points to critiq-rules/libs/rules/catalog/rules/go/go.security.unsafe-package-import.rule.yaml.