Code and Repository Monitors

Code and repository monitors in Sprinto ensure that your organisation’s source code management practices meet compliance and security requirements. These monitors track branch protection, code review enforcement, vulnerability scanning, and repository classification to help safeguard against unauthorised changes, insecure code, or compliance violations.

By enabling these monitors, Sprinto automatically validates repository settings across integrated platforms such as GitHub, GitLab, Bitbucket, and Azure DevOps.

---

What Sprinto Monitors

Sprinto checks repositories for:

• Branch Protection Rules Ensures branches have protection rules in place (e.g., no direct commits to main, mandatory pull requests).

• Code Review Enforcement Verifies that the pull request (PR) reviewer is different from the author, preventing single-user approvals.

• Vulnerability Scanning Tracks whether automated tools like Dependabot are enabled to detect vulnerabilities in dependencies.

• Repository Classification Confirms that all repositories are categorised (e.g., production, development, test) and critical repositories are explicitly identified.

---

Benefits

• Improved Code Security – Prevents insecure or unreviewed changes from being pushed into production.

• Compliance Readiness – Demonstrates evidence of secure coding practices and change management for audits.

• Developer Accountability – Enforces separation of duties between authors and reviewers.

• Early Vulnerability Detection – Flags security issues before code is deployed.

---

Supported Platforms

Sprinto integrates with:

• GitHub

• GitLab

• Bitbucket

• Azure DevOps

---

Next Steps

• Configure repository integrations in Sprinto.

• Review failing monitors to identify missing protections or misconfigurations.

• Apply branch protection rules, enable vulnerability scanning, and classify repositories as required.

• Re-run the monitor or upload evidence (where manual classification is required).