scan

You can scan repositories for deprecated golang usage by running automated bash scripts that check for ioutil deprecations, x/crypto usage, TLS compliance, and golangci-lint violations across target organizations to identify security gaps.

Automating compliance checks across large codebases is done by executing multi-tool scanners that evaluate Go versions, UBI usage, and TLS configurations while automatically pruning forks and abandoned repositories to reduce noise and aggregate findings into reports.

Yes, you can automatically create tracking issues for repository scan findings. The scanning process aggregates security and compliance results across repositories and optionally generates tracking issues to manage remediation tasks.

Yes, the repository scan automatically skips forks, abandoned repositories, and repositories without a go.mod file. This pruning and filtering mechanism reduces noise by ensuring only active, relevant Go projects are evaluated.

Available golang repository scanners include checks for TLS 1.3 compliance, x/crypto usage, gomock usage, ioutil deprecation, golangci-lint violations, Go version compliance, and UBI base image usage across targeted organizations.

You can check repositories for TLS 1.3 compliance by running the tls13-compliance-checker.sh script across your target organizations. This automated scan identifies non-compliant TLS implementations and reports findings for remediation.