ripple-sql 0.1.0__py3-none-any.whl

ripple_sql-0.1.0.dist-info/METADATA

@@ -0,0 +1,285 @@
+Metadata-Version: 2.5
+Name: ripple-sql
+Version: 0.1.0
+Summary: Offline column-level SQL lineage. See what breaks before you merge.
+Project-URL: Homepage, https://github.com/bteh/ripple
+Project-URL: Repository, https://github.com/bteh/ripple
+Project-URL: Issues, https://github.com/bteh/ripple/issues
+Project-URL: Changelog, https://github.com/bteh/ripple/blob/main/CHANGELOG.md
+Author: Brian Teh
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: data-engineering,dbt,impact-analysis,lineage,sql
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Database
+Classifier: Typing :: Typed
+Requires-Python: >=3.10
+Requires-Dist: jinja2<4,>=3.1
+Requires-Dist: pyyaml<7,>=6.0
+Requires-Dist: sqlglot<31,>=30.14
+Provides-Extra: benchmark
+Requires-Dist: acryl-datahub==1.6.0.16; extra == 'benchmark'
+Requires-Dist: openlineage-sql==1.52.0; extra == 'benchmark'
+Requires-Dist: sqllineage==1.5.8; extra == 'benchmark'
+Provides-Extra: dev
+Requires-Dist: lkml>=1.3; extra == 'dev'
+Requires-Dist: pytest-timeout>=2.3; extra == 'dev'
+Requires-Dist: pytest-xdist>=3.5; extra == 'dev'
+Requires-Dist: pytest>=8.0; extra == 'dev'
+Requires-Dist: ruff>=0.6; extra == 'dev'
+Provides-Extra: looker
+Requires-Dist: lkml>=1.3; extra == 'looker'
+Description-Content-Type: text/markdown
+
+# Ripple
+
+![Python](https://img.shields.io/badge/python-3.10%2B-blue)
+![License](https://img.shields.io/badge/license-Apache--2.0-green)
+
+**See what a SQL change breaks before you merge.**
+
+Point it at a dbt project or a folder of `.sql` files. It reads the SQL offline and answers the question you actually have:
+
+```console
+$ ripple breaks ecom.raw_orders.order_total
+
+8 columns in 6 models affected by ecom.raw_orders.order_total
+Hit hardest: stg_orders (2), orders (2), customers (1)
+
+  stg_orders · 2 columns · 1 hop
+    order_total_cents ← ecom.raw_orders.order_total
+    order_total ← ecom.raw_orders.order_total
+  orders · 2 columns · 2 hops
+    order_total_cents ← stg_orders.order_total_cents
+    order_total ← stg_orders.order_total
+  customers · 1 column · 3 hops
+    lifetime_spend ← orders.order_total
+  metric:order_total · 1 column · 3 hops
+    value ← orders.order_total
+  semantic:orders.order_total_dim · 1 column · 3 hops
+    order_total_dim ← orders.order_total
+  metric:lifetime_spend · 1 column · 4 hops
+    value ← customers.lifetime_spend
+```
+
+Four hops out it reaches `customers.lifetime_spend` and the two metrics built on it. Now you know before you touch it, instead of after someone's dashboard goes flat.
+
+The other direction, for when you inherit a table and have no idea where its numbers come from:
+
+```console
+$ ripple trace customers.lifetime_spend
+
+customers.lifetime_spend comes from:
+  orders.order_total → customers.lifetime_spend
+    stg_orders.order_total → orders.order_total
+      ecom.raw_orders.order_total → stg_orders.order_total
+```
+
+Both of those are real output from [dbt's own jaffle-shop](https://github.com/dbt-labs/jaffle-shop). Clone it and run them yourself.
+
+No warehouse connection, no account, no signup. Nothing leaves your machine.
+
+## Try it
+
+```bash
+# inside your dbt project or SQL repo
+uvx ripple-sql breaks stg_payments.amount
+```
+
+Or add it to your MCP client (Claude Code, Cursor, Codex, and others) as a tool:
+
+```bash
+claude mcp add ripple -- uvx ripple-sql mcp
+```
+
+Then ask: *"what breaks if I change `orders.amount` to cents?"* If the client
+lists ripple but the tools do nothing, `ripple doctor` tells you why.
+
+## Is it actually right?
+
+Most SQL lineage tools are confidently wrong, so Ripple ships a benchmark you can rerun instead of a claim you have to trust. Real public dbt projects, hand-verified column lineage, every tool scored by the same function. The corpus and the harness are both in this repo.
+
+| Round | cases | Ripple | DataHub | sqllineage | openlineage-sql |
+|---|---|---|---|---|---|
+| in-sample | 122 | **122 (100%)** | 98 (80%) | 38 (31%) | 30 (25%) |
+| held-out 1 | 54 | **27 (50%)** | 22 | 5 + crash | 8 |
+| held-out 2 | 62 | **29 (47%)** | 26 | 0 + crash | 4 |
+| held-out 3 | 56 | **26 (46%)** | 19 | 0 + crash | 3 |
+| held-out 4 | 56 | **16 (29%)** | 13 | 3 | 4 |
+| held-out 5 | 56 | 30 (54%) | **31** | 3 | 3 |
+| held-out 6 | 52 | 21 (40%) | **23** | 7 | 6 |
+| held-out 7 | 45 | **23 (51%)** | 17 | 0 + crash | 13 |
+| held-out 8 | 56 | **45 (80%)** | 24 | 11 | 7 |
+| held-out 9 | 42 | **26 (62%)** | 25 | 11 | 8 |
+| held-out 10 | 42 | **26 (62%)** | 20 | 10 | 8 |
+| held-out 11 | 46 | **7 (15%)** | 5 | 5 | 0 |
+| held-out 12 | 42 | **14 (33%)** | 14 | 0 + crash | 9 |
+
+Thirteen numbers, because any one alone would mislead you.
+
+The **in-sample** 100% means Ripple was debugged against those cases, so read it
+as "how far ahead on hard SQL shapes," not as an accuracy claim. The
+**held-out** rounds are the honest ones. Each is pre-registered: the repositories
+and commit SHAs are committed and pushed before anything is cloned, the ground
+truth is annotated by reading SQL only and independently re-derived by a second
+reader, it is frozen and pushed before any tool runs, and the round is scored
+once against a pinned commit and published as-is. Nothing is patched
+retroactively. Twelve rounds, eight dialects, and every miss classified in
+[`benchmark/HOLDOUT.md`](benchmark/HOLDOUT.md).
+
+Read the spread, not an average. Rounds are not poolable: each one samples a
+different corner of the world, so 15% and 80% are both true and neither is "the"
+accuracy. Conventional dbt projects score at or near perfect on first contact.
+Raw-SQL application repos are where every tool falls down, and where Ripple has
+its worst rounds too. Round 11 scored 15% because Ripple hit an engine crash on
+a versioned-migration estate, which is published in full along with the fix that
+followed. Round 12 was a tie. Round 5 and round 6 were losses.
+
+The consistent finding across twelve rounds is not that Ripple wins, it is that
+Ripple is right when it answers: recent rounds carry precision at or near 1.0
+with zero wrong edges, because the engine refuses instead of guessing.
+
+Nobody else in this space publishes a held-out score, and the one prior vendor
+benchmark kept its corpus private. Rerun ours, including the three tools Ripple
+is compared against:
+
+```bash
+uv pip install -e ".[benchmark]"   # sqllineage, DataHub, openlineage-sql
+python benchmark/fetch_corpus.py
+python benchmark/run.py
+```
+
+When Ripple isn't sure about an edge it says `review_required` instead of guessing, and that uncertainty follows the path: a result reached through one shaky hop is marked shaky even if the last hop looks clean. A typo'd name gets an error and a suggestion, never a false "nothing downstream."
+
+## Big repos
+
+`ripple doctor` spawns the server exactly the way a client does and tells you
+what's wrong: wrong python, something polluting the protocol stream, or a slow
+start. `ripple doctor --json` is the thing to attach to a bug report.
+
+Point it at a messy monorepo and it works out the shape itself. On a 2,600-file repo with 16 dbt projects nested at different depths, `ripple` with no arguments and no config found all 16, picked a dialect per project, and mapped 13,155 column links. The first run builds an index and takes a couple of minutes at that size. Every question after that comes from cache in about a second.
+
+## What it does
+
+- `ripple`: scan the project. Models found, links mapped, what needs review.
+- `ripple breaks <model.column>`: the blast radius. Every downstream column and model affected, plus row-level impact (filters, joins, and window keys that use it).
+- `ripple trace <model.column>`: where a column comes from, hop by hop, back to sources.
+- `ripple models` / `ripple columns <model>`: find the right names and see each column's fanout, so you know which columns are load-bearing before you touch one.
+- `ripple ci --base origin/main`: the blast radius of the models you changed, as a PR-ready comment. `--fail-on breaks` fails the build so a breaking change can't merge. `--select dbt` prints just the models to rebuild, so CI builds only what the diff actually touches:
+
+  ```bash
+  models=$(ripple ci --base origin/main --select dbt)
+  [ -n "$models" ] && dbt build --select "$models"
+  ```
+
+  Computed from git and column lineage: no state backend, no manifest artifact to stash between runs, no meter. dbt's own `state:modified+` rebuilds every descendant of any changed file; column lineage skips descendants that never read what changed. Anything uncertain (an unparseable diff, a changed row filter, a deleted model's readers) widens to `model+` instead of being skipped, so a missed rebuild can't happen silently.
+- `ripple graph -o graph.json`: export the full column-lineage graph.
+- `ripple breaks orders.order_total --open` (also `trace`): the answer as one self-contained page you can send, with a box to ask the next question. `--html PATH` writes it where you say.
+- `ripple ci --html PATH`: the same page for a whole change, one view per changed column; the GitHub Action attaches it to the run and links it from the comment.
+- `ripple serve` (or `ripple serve orders.order_total`): the same answer page, live, opening on the whole project. Every model sits in its layer from the source tables on the left to the dashboards on the right, with the links between them. Hover a model to light its chain, click it for its columns, click a column to ask. Type in the box to filter the map or to ask by name. Under the map, where coverage stands: which external tables still block links and whether query history has been brought in. Each answer comes from your files as they are now, so edit a model and ask again. Localhost only, read-only, nothing sent.
+- `ripple doctor`: verify this install can serve your MCP client, and print the exact config command with absolute paths.
+
+## Deterministic answers for AI-written SQL
+
+An agent will write SQL faster than you can review it, and "the run succeeded and the row counts matched" is not evidence that it wrote the right thing. Ripple is a parser, not a model. Ask it the same question twice and you get the same answer, with its uncertainty labelled.
+
+Run `ripple ci` on the pull request, or hand your agent the MCP server so it has to check its own
+blast radius before opening one.
+
+Ripple is built to be driven by an agent, so the line between what is parsed and what is predicted
+is written down and enforced: the engine never guesses, the agent may, and you always know which one
+is talking. [`docs/AI-BOUNDARY.md`](docs/AI-BOUNDARY.md) is the rule and the reasoning.
+
+## Bring your warehouse's schemas
+
+Ripple never connects to your warehouse. But your SQL probably reads tables defined outside the repo, and without their columns those models stop at `SELECT *`. Fix: your agent already has warehouse access, so let it fill the gap. Ask it to "resolve ripple's unresolved tables" and it will call `unresolved_tables`, fetch the columns from `information_schema.columns`, and hand them back via `ingest_schema`. They land in `.ripple/schemas.json`, which you can commit so the whole team gets the coverage.
+
+The credential boundary is the point. Your agent holds the connection; Ripple never does.
+
+No agent? Same thing by hand:
+
+```bash
+ripple unresolved                 # which tables block the most coverage, worst first
+ripple ingest-schema cols.csv     # CSV with a table,column header (or JSON, or - for stdin)
+```
+
+## Bring your query history (optional)
+
+Your SQL files say what is supposed to happen. The warehouse's query log says what
+actually ran. If `snow`, `bq`, or `databricks` is already set up on your machine,
+one command fetches and ingests it:
+
+```bash
+ripple collect-usage            # shows what's installed and configured
+ripple collect-usage snowflake  # your own queries, last 7 days, no permission needed
+ripple usage
+```
+
+Collect runs your warehouse CLI with the login you already have. Ripple reads
+connection names from its config, never a password or token, and never opens a
+warehouse connection of its own. The raw rows go to a temp file, get aggregated,
+and are deleted inside the same call; the query text is never stored and never
+passes through an AI model. When several connections are configured and none is
+your declared default, collect refuses and lists them instead of picking one.
+`--scope account` covers everyone's queries; if that needs a grant, the error
+contains the exact statement to hand an admin.
+
+No CLI set up? Export by hand and hand the file over:
+
+```bash
+ripple ingest-usage history.json
+ripple usage
+```
+
+Either way you get: which models actually ran in the window and which didn't, plus
+the tables your queries read that live outside this repo, which is activity the SQL
+files alone can't see (dashboards, scripts, other teams). `ripple usage` with no
+data prints the exact export SQL to run.
+
+Two honesty rules, enforced by tests. Ripple never says a model is unused; it says
+"not seen in this window" and prints the window, because in any short export a
+quarterly job looks identical to a dead one. And a statement with no database context
+is counted as "skipped rather than guessed" instead of being matched to whatever
+model shares its table's name.
+
+The export never goes through an AI model, and the query text is never stored: Ripple
+keeps per-table counts only. JSONL or a JSON array with a `query_text` field works;
+Snowflake's `QUERY_HISTORY` column names are understood as-is.
+
+## Does it fit my stack?
+
+**Reads:** dbt projects (with or without a compiled manifest), plain folders of
+`.sql` files, several dbt projects nested anywhere in one monorepo, LookML
+views, and dbt semantic models and metrics. Your orchestrator makes no
+difference; Ripple reads the repo, not the scheduler.
+
+**Dialects:** Snowflake, BigQuery, Databricks, Redshift, Postgres, DuckDB,
+Spark SQL. Detected per project, override with `--dialect`. Powered by
+[sqlglot](https://github.com/tobymao/sqlglot).
+
+**Partially:** SQL Server (T-SQL) views and table-valued functions trace;
+stored procedure bodies surface as a warning instead of wrong lineage.
+
+**Not today:** SQL written inside Python strings (Airflow operators, Superset,
+most Python ETL), DataFrame pipelines (PySpark, pandas), streaming, and
+BI-internal lineage (Tableau, Power BI). Pointing Ripple at a repo like that
+finds little or nothing, and it will tell you so rather than report an empty
+graph as if it were an answer.
+
+## Cost
+
+Ripple is Apache-2.0 and everything here is free. There is no paid version and
+no plan for one. The CLI stays account-free and telemetry-free, nothing phones
+home, and accuracy is never a paid tier. [`docs/VALIDATION.md`](docs/VALIDATION.md)
+shows how to verify that rather than take it on trust.
+
+## License
+
+Apache-2.0. Free to use, self-host, modify, and ship inside your own tooling.

ripple_sql-0.1.0.dist-info/RECORD

@@ -0,0 +1,72 @@
+ripple/__init__.py,sha256=5cAJlWeOj2eNp7j_oyU90TLP5kIjzqSDEeI_aNgzN6o,757
+ripple/answer.py,sha256=JqWPQSBbNBG6LJtlvDAKX9wd1xXvPzmQam08NpkSUUA,18832
+ripple/answer_page.py,sha256=U1-UUaB80_hQpE9DXO97IiXHfbCaQOl686iRV3AUK48,7254
+ripple/cache.py,sha256=5vVppjSpPQTgkEvrGHdqmFQcLf-3cWFDvTi6oFU0D3I,2759
+ripple/ci.py,sha256=5U8VG8jFT2UQbZuBzaeiYVwwwupR4_gEALqTRBt2hOw,16758
+ripple/ci_signature.py,sha256=iuJn5Yy8MhZ0RSG5-334tzRuEH4v_TABdj1VSi9-YG4,16392
+ripple/cli.py,sha256=mXOkRROrIaOiRaBqNroDUfIrqAhnCnmk2Ux3X6UZ-pU,26687
+ripple/doctor.py,sha256=nt-7k_Ytt-i6vafeVuu25ZmkNgLxmYAGMHAM5b0lJiE,7463
+ripple/graph.py,sha256=PjUUMj6LB9WjLbwO5SLj4l4GTfFjXdEyqcM5ewVUP8g,70354
+ripple/home.py,sha256=WBSEOQtW9gpXIHexWYL3J9utjR1riGOhU5cMlQtP7xM,8930
+ripple/lookml.py,sha256=0szM4SMwqGCKuHL5tz210h-JaOsX7K_5eMZIMigcbG8,5956
+ripple/mcp_server.py,sha256=b-fiwH8pN-7cPDl2kChL1HeG2NtC2B0809C75IMEoEQ,26460
+ripple/names.py,sha256=abzRMRK7824hI_jfvLl60Gmxt9H6Tkn7GGSqowaDeEs,1518
+ripple/project.py,sha256=y20FfRuJo9YR6IESXI54oxfww2zjbFAIgj6r1wcrcwc,6646
+ripple/py.typed,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
+ripple/render.py,sha256=TWhpxrU0_tWPWCczTNlTBwNe10ZLKZNinirKC5XjdC0,15004
+ripple/render_shims.py,sha256=eLz5EjjaiahXCHYpJXCfgyFy0jBzT1j9mZXKMEfx65U,8421
+ripple/schemas.py,sha256=pq5NIEaE8wdUhuywsCPFw7buezAwd60Ljt7GFpy9vAk,6195
+ripple/semantic.py,sha256=NFgcqh0H03NDUmist_1qQQZyC4cm6nVyEaMb2GosI7A,9259
+ripple/server.py,sha256=YbHNYNxDs6p3YxacnLxQ3-IVDSVF06UW7d-QoNgMaKQ,7113
+ripple/sourcefiles.py,sha256=PMLdTZ13RZNtzgNP6H37NsqpoEp3iu094pghJ99NAzY,2057
+ripple/star_resolution.py,sha256=RlXavwHC339YtDO7hysH6YmcfMMAf8R4y5cH3ca-mvI,4169
+ripple/engine/__init__.py,sha256=ezlR6frqjG5HQx-w6X9v6mhdKbqOx-aDiDBMTCR2Zw4,3282
+ripple/engine/budget.py,sha256=-8T8w_yML4C335-lpZDDbu555KmYrGOmhHavHaG57LU,2854
+ripple/engine/column_lineage.py,sha256=tU5f2TH9rxQD9CbNpf07Sm8LlbAbu7m6vvpYoeGi7dw,3062
+ripple/engine/column_ref.py,sha256=TpEuaRCg3iGxzyZ8L_ViMn1sSWhsUUtxFWZoJz7QY24,35071
+ripple/engine/cte_tracing.py,sha256=jRtLEGrKzs30DfdOU_aY3yR3p9d75U9b0dRE1X9-36Y,56001
+ripple/engine/dependencies.py,sha256=D_l7s8MDAhx23ummpusRj-ckabkrKgtn7kH1pPt-qy8,15474
+ripple/engine/dialect.py,sha256=oEH4YBQITKq0xY5choTKZvANmSJWc7v5urVQcmEbKPk,4264
+ripple/engine/dispatch.py,sha256=mC6DDHM0wH9T2l24Spq9JmglaoRO_iCjRtY2a0THHvo,357
+ripple/engine/extraction.py,sha256=PWj-JRFe22v6VxKpBCX7hzRuQmdG11jyeFeK-9fHh5o,1062
+ripple/engine/jinja.py,sha256=tHHUyNhlHS0JMErCI4rrCEeO6jW8dPckvfRirdbBlBg,10306
+ripple/engine/json_sources.py,sha256=WnrOeDoNltXTixtbHxW-AHXnSreK2JAqXyp3xShRY54,9665
+ripple/engine/macro_source.py,sha256=XeC983ehOkJ15zaIrb3uVYYQXQ0P1oepmhnZIE3yxPw,4195
+ripple/engine/pipeline.py,sha256=WrYxdRrwaO2JkZZxx1MnxQD2TLIyIpB6TYha57xEn7s,10130
+ripple/engine/preprocess.py,sha256=OXzJcVyFBBQMxvd8KsuStv9bjXp7992xi-qh-ohnq0E,7042
+ripple/engine/safe_gen.py,sha256=6p0SJTDNvtypsNPeR07Dy-cRF4UFVtfDZfxUZTDY0dM,741
+ripple/engine/schema_qualification.py,sha256=ur6tk4PsG5nJ-Zx9Hm4C8k9LjAbV6MAoD-pD7Ymz1OM,5091
+ripple/engine/scope.py,sha256=OK2q-bZo359AAcTUMBwhA07keGgHKoIXls6ja_zmF_I,23257
+ripple/engine/select_sources.py,sha256=vjQdY1e38hGl2F-Qh-pvCQGApcI8Ggg6q596-WlIhVw,48521
+ripple/engine/sql_script.py,sha256=oef6UX6QprVQI_WHf-GkbLg0qs-z5jtyvsYdkZ4O6Gs,30611
+ripple/engine/statement.py,sha256=3QMQp3eiTMoQ-ris-3tbIuvVFCR9sBblOf6Imd3fU8U,19356
+ripple/engine/tech_debt.py,sha256=L_6dJylRSfyoGe37-max2Cgj0yIVSkJnXYAnTodq-Bk,6003
+ripple/engine/tsql_catalog.py,sha256=e715W_7Vi_DE1RWSqyxNBBnnvWu8uMVWhTLy692EyV8,2744
+ripple/engine/tsql_scalar_vars.py,sha256=aIJbJTj09sXLhkvGic7Tlp0PwMc6hS0ZfpwfHT8YQUM,10201
+ripple/engine/tsql_tvf.py,sha256=Y77X8WX7Exrib31-8yNAvBEnoNcL5XiJ28qqlHkzwO0,23577
+ripple/engine/tsql_xml.py,sha256=yPL0rSWDGLCz5wsDggd4Mhu0fgJcuSbA6O2E7yhs_KI,3717
+ripple/engine/types.py,sha256=D7f7JfGUx6837Y8iKniWrIa3L5OFNQpETP8EcssvCII,6534
+ripple/engine/unused_deps.py,sha256=vxEl1Dz4-sDyZBu97ICReXax-NTayaeujBQP4OR5ZpA,21465
+ripple/engine/validation.py,sha256=f1nuG-APJHIWfx2IqWNxM0F6yHK5HdmTJaZ7BhCK9Tg,5111
+ripple/loaders/__init__.py,sha256=cXE6xb6XKA3EbsdzWX-O3KmWsNA_sTohoZ2E0_T365Q,343
+ripple/loaders/dbt.py,sha256=3jK8vcrwcu4-nWhvKFv3KxiOewQr1_BHeneIX1U6J28,13910
+ripple/loaders/dbt_config.py,sha256=rNN1vtkPDg7xXqG1PZRqSnLhUkUICWlSShIpyBwNq1U,12532
+ripple/loaders/identity.py,sha256=gHB3M3hpsCRWVytYMsPAakJbVvU7HGv3MjbTnvV8xCE,15156
+ripple/loaders/sidecar.py,sha256=0cES2az-FudezBXjSBYLUhmQD099ISuChvgy12lThdo,2477
+ripple/loaders/sqldir.py,sha256=PN8Bae6cQGpxurx4TT25dSvRs8PKRAgteskwIac2eEA,11454
+ripple/loaders/types.py,sha256=nW9Tng9WS_ufDKJWXxda91kFwyg8YM23w-B066pD_vE,7885
+ripple/static/answer.css,sha256=sUET2y27VfjBJOkUnvR-bYACqtc1fTSrhJnX6nVTZJE,11312
+ripple/static/answer.html,sha256=ZDh9QSbnw-VyRWOTPJ9MEgtPPKMXK-Tv5TM6NwNzimE,19676
+ripple/static/answer_twin.js,sha256=358KxFJLn-KFzSyvAzKuGRaNMNDlWW6HUNfKNAERU5Y,18143
+ripple/static/explore.js,sha256=nTTyPMlBhoGF7zmYB6tWCvwR2CIlxh2p5s1acAqNEsY,6650
+ripple/usage/__init__.py,sha256=hMojHlN1PlYtxzYQ-u2ZGr65by790Q8zJOzueKLhtGs,855
+ripple/usage/cli.py,sha256=311WqqSOMXmHJeCj3KmIG1mPvtoOahTEe4dpFt6AtVo,2925
+ripple/usage/collect.py,sha256=gVDGR3z8xCFn0oDKRy8baXnUFxKkiKFmtt9E6uBI77E,13247
+ripple/usage/discover.py,sha256=8FtLEGtd6ymxboTWZKwHvZS2UsPq0cavYeXrPm0I_ZY,7163
+ripple/usage/ingest.py,sha256=JaBfJ21ETY_H3NWswlTvrAFm73PHYjn3iCgNt85SHhw,15234
+ripple/usage/report.py,sha256=qChKLqk7pJESZgAdQLHMvDdO7-ftISIrU71a-j_3Mts,5520
+ripple_sql-0.1.0.dist-info/METADATA,sha256=7oo904wzEEBqE8R_5xj9fEQHHUHJOkYDBr3cS6w6EWU,15180
+ripple_sql-0.1.0.dist-info/WHEEL,sha256=zOwg4jB6zX2kU910N-cMawjivD6tO8NEWvE12je1bVk,87
+ripple_sql-0.1.0.dist-info/entry_points.txt,sha256=Ey-SNOmWtqzOdvI4z8nw_CqR3sdbQVjU9cfxJCg95SU,72
+ripple_sql-0.1.0.dist-info/licenses/LICENSE,sha256=pVdJHLJkgn4Pb6e-LZTHWlEvmq-Oy8_ttZ3gkoArbK8,11340
+ripple_sql-0.1.0.dist-info/RECORD,,

ripple_sql-0.1.0.dist-info/WHEEL

@@ -0,0 +1,4 @@
+Wheel-Version: 1.0
+Generator: hatchling 1.32.0
+Root-Is-Purelib: true
+Tag: py3-none-any

ripple_sql-0.1.0.dist-info/entry_points.txt

@@ -0,0 +1,3 @@
+[console_scripts]
+ripple = ripple.cli:main
+ripple-sql = ripple.cli:main

ripple_sql-0.1.0.dist-info/licenses/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Brian Teh
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.