What do GitHub Advanced Security license usage views help administrators manage?
Select an answer to reveal the explanation.
Short Explanation
GHAS is licensed by active committers, so usage views show who's consuming those licenses across repositories. You can enable security features deliberately, keep seats in compliance, and control costs. It isn't a TLS off switch or a desktop conversion kit.
Full Explanation
The correct answer is tracking how many committers are consuming GHAS licensing across repositories so seats/committers stay in compliance. GHAS is licensed by active committers, and usage views show who is burning those licenses. Admins enable GHAS where risk warrants and monitor unique committer counts. The option about disabling TLS on all endpoints safely is false. The option about removing the need for CODEOWNERS is false. The option about converting GHES into a desktop app is false. Exclude archival noise repos if policy allows, communicate enablement standards, and reconcile billing monthly. Pair license visibility with security overview so you aren't paying for scanning you never remediate, and so high-risk repos aren't left unscanned solely to save a few committer seats.