unity-catalog-and-lakehouse-governance — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited unity-catalog-and-lakehouse-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 Unity Catalog is the core governance surface for a Databricks platform. It helps agents design governed boundaries across catalogs, schemas, storage locations, shares, and access paths for lakehouse data products.
Unity Catalog hierarchy and ownershipDelta tables, views, volumes, or modelsDo not reduce Unity Catalog to permissions only. It is also a publish, ownership, and operating-boundary decision.
Decide:
Cover:
Include:
Require:
Review how promotions, new workspaces, external consumers, and object-store boundaries behave under the governance model.
| Rationalization | Reality |
|---|---|
| "We already use Databricks, so Unity Catalog design is obvious." | Poor catalog and location design creates long-term friction in ownership, sharing, and environment boundaries. |
| "We can give broad workspace access and tighten later." | Over-broad access becomes hard to unwind once shared data products are adopted. |
| "Lineage comes for free." | Platform lineage is useful only when publish boundaries and ownership are designed intentionally. |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.