Skip to content

Datalineage bigquery asset impact analysis vs Supabase rls policies

Datalineage bigquery asset impact analysis is an open-source agent skill for databases. Supabase rls policies is an open-source agent skill for databases.

  • Supabase rls policies has more GitHub stars (41,254 vs 24,379).
  • Datalineage bigquery asset impact analysis is best for check what breaks if a bigquery table is dropped.
  • Supabase rls policies is best for lock down a new notes table so each user sees only their own rows.
What it is
Datalineage bigquery asset impact analysis is an open-source agent skill for databases.
Supabase rls policies is an open-source agent skill for databases.
Best for
Check what breaks if a BigQuery table is dropped
Lock down a new notes table so each user sees only their own rows
Kind
Skill
Skill
Pricing
Open source
Open source
Platforms
Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf, Goose
Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf, Goose
GitHub stars
24.4K
41.3K
Last commit
Nov 2026
Nov 2026
License
Apache-2.0
MIT
Open source
Good for
Check what breaks if a BigQuery table is dropped; Find dashboards that depend on a stale view; List downstream tables before pausing a scheduled pipeline
Lock down a new notes table so each user sees only their own rows; Review a migration that changes RLS policies on a Supabase project; Write pgTAP tests proving two users cannot read or edit each other's data

What Datalineage bigquery asset impact analysis does

  • Downstream lineage discovery

    Retrieves downstream tables, views and processes that depend on a BigQuery asset through the lineage server.

  • Blast radius table

    Produces a Markdown table of affected assets with transform process, depth and impact type.

  • Critical path highlighting

    Flags production, dashboard, reporting and master assets based on their names.

  • Location resolution

    Finds the dataset location with bq show and falls back to asking the user if that fails.

  • Search transparency

    Reports the locations, parent path, depth limit and process limit used in the search.

What Supabase rls policies does

  • Per-operation policy design

    Writes separate select, insert, update and delete policies scoped to the authenticated role.

  • Owner column enforcement

    Binds the owner column in insert and update checks so users cannot assign rows to others.

  • Two-user pgTAP tests

    Provides a test template that signs in as two users and checks each read and write attempt.

  • Policy failure verification

    Adds a temporary open policy on a local database to confirm the tests catch overly broad access.

  • View and function review

    Covers security_invoker views and search_path hardening for security definer functions.

  • MFA-restricted access

    Shows how to add a restrictive policy that requires an aal2 session.

Datalineage bigquery asset impact analysis vs Supabase rls policies: questions

Is Datalineage bigquery asset impact analysis or Supabase rls policies cheaper?

Both are open source. Compare current plans on each official site.

What is the difference between Datalineage bigquery asset impact analysis and Supabase rls policies?

Datalineage bigquery asset impact analysis is an open-source agent skill for databases. Supabase rls policies is an open-source agent skill for databases. Supabase rls policies has more GitHub stars (41,254 vs 24,379).