TT-17667: enforce Sonar lint rules

[olamilekan000]

Description

change updates golangci-lint configuration so existing
SonarCloud analysis receives security and deprecated-import findings.

Related Issue

https://tyktech.atlassian.net/browse/TT-17667

Motivation and Context

How This Has Been Tested

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Refactoring or add test (improvements in base code or adds test coverage to functionality)

Checklist

• I ensured that the documentation is up to date
• I explained why this PR updates go.mod in detail with reasoning why it's required
• I would like a code coverage CI quality gate exception and have explained why

Ticket Details

TT-17667

Status	In Dev
Summary	Enforce Sonar rules consistently across all repositories

Generated at: 2026-07-06 09:17:07

[sentinelone-cnapp-eu1]

SentinelOne CNS Hardcoded Secret Detector
✅ Congratulations, your code is safe

SentinelOne CNS is a cloud-agnostic, agentless CSPM & CWPP solution that continuously detects and prevents vulnerabilities that have the highest probability of being exploited in Azure, AWS, Google Cloud, and Kubernetes.

[probelabs]

This PR updates the .golangci.yml configuration to enable two new linters, gosec and depguard, enhancing the project's static analysis for better security and code health.

Files Changed Analysis

• .golangci.yml: Modified (+10 additions) to enable and configure the new linters. This is the only file changed.

Architecture & Impact Assessment

• What this PR accomplishes: It integrates security scanning and enforcement against deprecated packages directly into the CI linting process. This helps prevent new security vulnerabilities and deprecated code from being introduced.
• Key technical changes introduced:
  • gosec linter: Enabled to perform security analysis on the Go source code.
  • depguard linter: Enabled and configured with a rule to deny the use of the io/ioutil package, which has been deprecated since Go 1.16.
• Affected system components: The primary impact is on the development workflow and the CI pipeline. All future code contributions will be subject to these new rules. There is no direct change to runtime components, but the overall code quality and security posture of the application will be improved over time.

Scope Discovery & Context Expansion

• The impact of this change is repository-wide, as the new linting rules will apply to all Go files. This may require refactoring in existing code or open pull requests that use the io/ioutil package.
• To understand the immediate effort required, a codebase search for "io/ioutil" would identify all files that need to be updated. It would also be valuable to run the new linter configuration across the master branch to get a baseline report of any existing issues flagged by gosec.

Metadata

• Review Effort: 1 / 5
• Primary Label: chore

---

Powered by Visor from Probelabs

Last updated: 2026-07-06T09:17:47.319Z | Triggered by: pr_opened | Commit: e0a526b

💡 TIP: You can chat with Visor using /visor ask <your question>

[probelabs]

✅ Security Check Passed

No security issues found – changes LGTM.

✅ Architecture Check Passed

No architecture issues found – changes LGTM.

✅ Security Check Passed

No security issues found – changes LGTM.

\n\n

✅ Architecture Check Passed

No architecture issues found – changes LGTM.

\n\n

✅ Performance Check Passed

No performance issues found – changes LGTM.

---

Powered by Visor from Probelabs

Last updated: 2026-07-06T09:17:40.874Z | Triggered by: pr_opened | Commit: e0a526b

💡 TIP: You can chat with Visor using /visor ask <your question>

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud