Check ID:
Provider: GitHub
Service:
Severity: HIGH
Categories:
Resource type:
repository_dependency_scanning_enabledProvider: GitHub
Service:
repositorySeverity: HIGH
Categories:
vulnerabilities, software-supply-chainResource type:
NotDefinedWhat this check verifies
GitHub repositories are assessed for dependency vulnerability scanning enabled viaDependabot alerts, which monitors the dependency graph for known vulnerable packages and versions.
Risk
Without automated scanning, known vulnerable dependencies may persist unnoticed, enabling supply-chain compromise. Exploits in third-party libraries can drive RCE, data theft, or build tampering, undermining confidentiality, integrity, and availability across code and CI/CD.Recommendation
Enable dependency vulnerability scanning withDependabot alerts or an equivalent SCA tool across repositories. Apply defense in depth: keep manifests and lockfiles current, triage alerts quickly, use automated security updates with required reviews, and surface results in PR checks and notifications.
Remediation
- CLI
- Terraform
- Dashboard steps
gh api —method PUT repos/<OWNER>/<REPO>/vulnerability-alerts
References
Where this check fires
This check runs on every scheduled scan against your GitHub account. Findings appear at Cloud Security → Findings filterable byCheck ID = repository_dependency_scanning_enabled. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to GitHub checks