Am I the only one who finds the compliance dashboard too noisy for daily use?

Our team's primary use case is license compliance for Kubernetes deployments. The dashboard is drowning us in low-priority data.

We get alerts for every transitive dependency with a `BSD-3-Clause` license, which is fine for our final bill of materials but creates constant noise. The critical issues (like `GPL-3.0` in a core service) get lost.

Has anyone tuned this to be actionable?
* Effective suppression rules for common, accepted licenses?
* A way to surface only policy violations, not every single license?
* Is the intended workflow just to ignore the dashboard and rely solely on the API/reports?

The default view feels built for an audit, not for daily engineering oversight.