Silent updates (90d)

count

Count of unannounced behaviour changes detected by canary pipeline in 90 days

What is silent updates (90d)?

Count of unannounced behaviour changes detected by canary pipeline in 90 days

Why it matters

Understanding silent updates (90d) helps developers make informed decisions when evaluating models and providers. This metric provides a concrete, comparable data point — removing guesswork from the selection process. When you know the numbers, the data decides.

Where models stand

No data available yet for this metric.

How sourc.dev tracks this

sourc.dev tracks silent updates (90d) through its automated monitoring pipeline. Data is collected on a regular schedule, compared against previous values, and any changes are recorded in the history table with full provenance — source URL, effective date, and verification timestamp. Nothing is overwritten. The pipeline ensures this attribute stays current without manual intervention.

Related

Frequently asked questions

How does sourc.dev measure silent updates (90d)?

sourc.dev monitors this attribute automatically via pipeline. Every data point includes a source URL and verification date. Changes are recorded in the history table — nothing is overwritten.

How often is silent updates (90d) updated?

This attribute is monitored on a regular schedule by automated pipeline. Changes are detected and recorded automatically.

Why does silent updates (90d) matter for developers?

Understanding silent updates (90d) helps developers make informed decisions when choosing between models and providers. Rather than relying on marketing claims, sourc.dev provides verified, dated, source-linked data so the data decides.

← Back to Knowledge Library