Skip to main content
SAICA-KG

Failure modes

Obsolescence

Using deprecated APIs, retired packages, or outdated library versions — often because the model's training data pre-dates current releases.

a.k.a. stale-training-knowledgea.k.a. training-cutoff-drifta.k.a. version-drifta.k.a. deprecated-api-usagea.k.a. library-evolution-lag

Description

The agent emits code that references real APIs or packages that have been deprecated, removed, or materially changed in their recommended version. The root cause is frequently training-data staleness: the model saw a library version that has since been superseded, and it confidently emits the older form. Distinct from fabrication (non-existent) and from dependency_blindness (real-and-current-but-ignored).

Detection signals

Prior work

Crosswalks

Related failure modes

Mitigating tools

View raw YAML on GitHub →