GitHub has started running security risk assessments automatically for organizations using its Team plan, giving administrators a way to inspect exposed credentials and code vulnerabilities without first initiating an assessment.
The company announced the change on November 18. Organization administrators and security managers can review the findings, which GitHub describes as part of its free security risk assessment offering.
Detection does not equal remediation
An automatic assessment identifies possible risks for review. It does not itself establish that a leaked credential has been revoked, a vulnerable dependency upgraded or a code flaw repaired.
GitHub’s announcement does not provide a count of organizations newly covered, the frequency of reassessment or comparative detection rates. Those omissions limit any claim about how much the change reduces security incidents.
Different from this week’s AI Scan updates
GitHub separately introduced controls to enable AI Scan through its API on November 13 and bulk initiation for up to 20 repositories on November 16. The November 18 Team announcement concerns automatic security risk assessments rather than a claim that all AI scans now run without user action.
Administrators should review the findings and distinguish confirmed exposures from items requiring further investigation. The release does not state that the assessment replaces existing code scanning or secret-scanning policies.
The change is available to organizations on GitHub Team, according to the company’s release.



















