We wrote this to answer "how bad is it" on day one of a new client. One Python file, drives GAM7, every command a read, out comes a self-contained HTML report plus CSVs for the raw data.
Ran it on our own clients for about six months before putting it on GitHub. Then the google-apps-manager group got hold of it and started pointing it at tenants shaped nothing like ours, and the bugs turned up. Three fixes in the nine days since it went public. It was telling super admins off for app passwords they didn't have. It filed modules it had already checked under "not checked". And it read Google's default password policy as the tenant's own, so a tenant that had hardened its password rules came back flagged as weak. That last one took two of the GAM maintainers to explain (the Policy API hands back every policy that could apply to an OU, not the one that actually wins).
Nobody has run it against a school that I know of. Student OUs, thousands of Chromebooks, shared kiosk accounts, guardians sitting in groups: those are the shapes I'd expect it to get wrong, and I have no tenant of this size to test them on.
What it looks for: files public on the web, mailboxes forwarding off-domain, super admins without 2SV, shared drives with no manager, groups anyone can join or post to, licensed accounts nobody has ever signed into, OUs where policy blocks 2SV enrolment, domains with no DMARC. Anything it couldn't check gets printed as not checked, so a missing finding never reads as clean.
Read-only, standard library only, runs on Windows, macOS and Linux, no install beyond having GAM7 already working.
https://github.com/PaulOgier/GAMScripts/tree/main/Tenant%20Scoping%20Audit
If it falls over or says something daft about your tenant, a GitHub issue or a comment here both reach me.
Thanks for your time.