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.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/vinta/awesome-python/pull/2912
**Author:** [@gauthierpiarrette](https://github.com/gauthierpiarrette)
**Created:** 2/12/2026
**Status:** ❌ Closed
**Base:** `master` ← **Head:** `master`
---
### 📝 Commits (1)
- [`24c821f`](https://github.com/vinta/awesome-python/commit/24c821f399ad94e1cc589b1e7007dd441c80b090) Add timefence to Data Validation
### 📊 Changes
**1 file changed** (+1 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `README.md` (+1 -0)
</details>
### 📄 Description
## Project
[Timefence](https://github.com/gauthierpiarrette/timefence)
## Checklist
- [X] One project per PR
- [X] PR title format: `Add project-name`
- [X] Entry format: `* [project-name](url) - Description ending with period.`
- [X] 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
- [X] **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.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/vinta/awesome-python/pull/2912
Author: @gauthierpiarrette
Created: 2/12/2026
Status: ❌ Closed
Base:
master← Head:master📝 Commits (1)
24c821fAdd timefence to Data Validation📊 Changes
1 file changed (+1 additions, -0 deletions)
View changed files
📝
README.md(+1 -0)📄 Description
Project
Timefence
Checklist
Add project-name* [project-name](url) - Description ending with period.Why This Project Is Awesome
Which criterion does it meet? (pick one)
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.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.