Skip to content

GoldenMatch

v0.5.0 Feature

This release adds 2 notable features for engineering teams evaluating rollout.

Published 4mo Data Pipelines & ETL
✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

data-cleaning data-engineering data-matching data-quality deduplication entity-resolution
+14 more
fellegi-sunter fuzzy-matching knowledge-graph llm master-data-management mcp-server polars pprl python record-linkage rust splink typescript zero-config

Summary

AI summary

Updates Stats, What's Next, and 0.75-0.95 across a mixed release.

Full changelog

Phase 1 of the v1.0.0 Roadmap

In-Context LLM Clustering

Instead of asking the LLM "is A the same as B?" one pair at a time, GoldenMatch now sends blocks of 50-100 borderline records in a single prompt and asks the LLM to cluster them directly. The LLM sees all candidates at once and can make better group decisions.

llm_scorer:
  enabled: true
  mode: cluster          # new! (default: "pairwise" for legacy behavior)
  cluster_max_size: 100
  cluster_min_size: 5
  budget:
    max_cost_usd: 0.50

How it works:

  1. Traditional pipeline scores all pairs as usual
  2. Borderline pairs (0.75-0.95) are grouped into connected components
  3. Each component is sent to the LLM as a single prompt
  4. LLM returns cluster assignments with confidence scores
  5. Results merge back into the pipeline seamlessly

Smart degradation: If a block is too large, it splits by removing weakest edges. If the LLM call fails, it falls back to pairwise scoring. If the budget runs out, it stops gracefully.

Uncertainty Scores

Every LLM cluster now carries a confidence score (0.0-1.0) from the LLM. Low-confidence clusters (< 0.7) are auto-flagged for human review.

Stats

  • 875 tests passing (20 new, 0 regressions)
  • CI green on Python 3.11/3.12/3.13

Install / Upgrade

pip install --upgrade goldenmatch

What's Next

  • v0.6.0: Privacy-preserving record linkage (multi-party SMC)
  • v1.0.0: API freeze, production-stable release

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track GoldenMatch

Get notified when new releases ship.

Sign up free

About GoldenMatch

All releases →

Related context

Related tools

Earlier breaking changes

  • v3.1.0 `GOLDENMATCH_FRAME=polars` now requires the `[polars]` extra; raises error without it.
  • vgoldencheck-v3.0.0 `inferred_type` emits neutral dtype vocabulary (str/int/uint/float/date/datetime/bool/other) instead of raw Polars dtypes.
  • vgoldencheck-v3.0.0 'inferred_type' now emits a neutral dtype vocabulary instead of raw Polars dtype strings.
  • vgoldencheck-v3.0.0 `scan_file`, `scan_dataframe`, and CLI `check` now run without Polars, using Arrow-native pyarrow.Table.
  • v3.0.0 Result frames now return pyarrow.Table instead of Polars DataFrame.

Beta — feedback welcome: [email protected]