Quick question on License Compliance from our Enterprise trial evaluation. Our understanding from your documentation was that a fresh ProGet install ships with some kind of default policy flagging GPL/copyleft licenses for review. On our fresh Enterprise trial instance, that wasn't the case — a package we tested (MySql.Data 8.4.0, correctly detected as GPL-2.0-only) was Compliant by default, with no Specified License Rule in place at all until we added one ourselves.

Once we added a rule marking GPL-2.0-only as Noncompliant, enforcement worked exactly as expected — the same real 400 Bad Request block we see for vulnerability-based quarantine applied identically.

Is a default GPL/copyleft rule meant to be pre-configured out of the box, and we're missing a setup step, or is that something every install needs to configure explicitly regardless of edition? Want to make sure we don't have a false sense of security assuming default license enforcement exists when it doesn't.

Thanks,
Sai