Hook community intermediate
Freshness Pre-Merge Check
Warn when a change would silently widen the freshness SLA of a source.
At a glance
| What | Warn when a change would silently widen the freshness SLA of a source. |
|---|---|
| Where | Data Observability |
Purpose
Warn when a change would silently widen the freshness SLA of a source.
Security scan
Last sweep 2026-10-24: 0 finding(s), 0 marked as examples.
Implementation
Compare the schedule/cron in the diff with the source's declared freshness SLA. If the new schedule can produce data older than the SLA (e.g. daily when the SLA is 6h), warn with the computed worst-case lag.
Registry stats
| Verification | community · Sep 18, 2026 |
|---|---|
| Completeness | 74 |
| Trust multiplier | ×0.75 |
| Composite | 31.1 · adequate |
| Freshness | 36 days since last source check |
| Difficulty | intermediate |
| Version | 0.1.1 |
| License | Apache-2.0 |
| Security flags | 2 |
Example
Changing a source cron from hourly to daily warns that the 6h freshness SLA will be violated.
Did this solve your problem?
Freshness Pre-Merge Check