You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Two risk worklists derived from one ranking, in the report data (worklists.changeFrontier: changing fast, unproven; worklists.irreversible: can destroy data, unproven). The scoring formula is unchanged — a multiplicative top-20 cannot hold both families, so both are now available; on-page rendering follows in 0.2.37
Destructive-sink detection by call shape: delete/purge/drop/destroy through any receiver field; remove* only through a persistence-shaped field; chained calls and past participles (DeletedRuleRetentionTime) are not sinks
Risk rows now read in plain English: the consequence, what the graph saw (naming the actual sink callee), and what would close it; the formula in words at the end
rank_exclude_paths in .orangepro/config.json: exclude a scope (e.g. ui/**) from the ranking without touching the denominator
TypeScript repos retain unresolved external callees by name, matching Go — no new nodes or edges
Evidence tiers, proof oracle, compile gate, and the P×I×D formula are untouched