Add timefence

[gauthierpiarrette]

Project

Timefence

Checklist

• One project per PR
• PR title format: Add project-name
• Entry format: * [project-name](url) - Description ending with period.
• Description is concise and short

Why This Project Is Awesome

Which criterion does it meet? (pick one)

• Industry Standard - The go-to tool for a specific use case
• Rising Star - 5000+ stars in < 2 years, significant adoption
• Hidden Gem - Exceptional quality, solves niche problems elegantly

Explain:

Temporal data leakage is a silent killer in ML: a standard LEFT JOIN can leak future data into training, inflating offline metrics while production fails. No error, no warning. Timefence is the only tool purpose-built to detect and fix this. It audits existing datasets or builds correct ones, runs on DuckDB with zero infrastructure, and plugs into CI/CD with one line.

How It Differs

If similar entries exist, what makes this one unique?

Data validation tools (Great Expectations, Soda) check schema, nulls, and distributions - not temporal correctness. Feature stores (Feast, Tecton) serve features at scale but don't validate point-in-time correctness. Timefence fills the gap: a lightweight, dedicated tool for catching when feature_time > label_time.

[JinyangWang27]

@gauthierpiarrette Thank you for your submission. Unfortunately, this PR doesn't meet our acceptance criteria:

Repository age: The repository was created a week ago. We require a minimum of 3 months (or 6 months for Hidden Gem submissions) to ensure project stability.
GitHub stars: 2 stars (minimum 100 required, or strong justification for Hidden Gem).

Please see our CONTRIBUTING.md for full requirements. You're welcome to resubmit once the project has matured and gained community traction.