dataplex-and-bigquery-governance — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited dataplex-and-bigquery-governance (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Use this skill when governance on GCP is centered on Dataplex, BigQuery, and related Google Cloud metadata controls. It helps agents define governance zones, policy-tag boundaries, lineage expectations, and trusted publishing patterns for warehouse and lake platforms.
Dataplex lakes, zones, or governance domainsBigQuery policy tags and governed publish boundariesGCPCloud Storage, BigQuery, Dataflow, and DataprocDo not treat BigQuery governance as only a permissions problem. Trusted publishing also needs metadata, ownership, and policy boundaries.
Decide:
Include:
Make explicit how Cloud Storage, BigQuery, and processing services fit the same control model.
Require:
Review whether onboarding, schema evolution, and new domains remain manageable under the governance model.
| Rationalization | Reality |
|---|---|
| "Policy tags are the whole governance design." | Tags help, but they do not replace ownership, zone design, trusted publishing, or metadata quality. |
| "Dataplex is only for lake governance." | Many teams need a joined governance model across storage, warehouse, and processing surfaces. |
| "Discovery will happen automatically once assets are scanned." | Useful discovery requires curated metadata and trust signals. |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.