Skip to main content

Overview

You get a 0–100 composite risk rating for every vault (0 = safe, 100 = critical). The rating is built from approximately 20 sub-ratings, each weighted by importance. Additionally, additive penalties and hard state floors can raise the rating for binary danger conditions. Higher always means riskier. Every number in the rating can be traced back to a specific signal. The API exposes the full sub-rating breakdown so you can tell a user “this vault rates 78/100 because redemptions are currently closed and the admin key is an EOA with no timelock” — not just a number.
For endpoint usage, query parameters, and response format, see the Vault Risk API Reference.

Final Outputs


Sub-Ratings

Each sub-rating is 0–100. The weight shows how much it contributes to the final composite.

Contract & Code Quality

Governance & Control

Liquidity & Exit

Performance & Market Behavior

Oracle Type Quality

Oracle quality contributes 3% to the composite. The sub-rating uses a weakest-link model — the worst oracle type found across the vault’s underlying markets sets the floor.
Any collateral token with less than $5M daily trading volume raises the oracle sub-rating floor to 55 (thin_collateral_market flag). Below that volume threshold, a well-capitalised attacker can move the price enough to overborrow against inflated collateral — the pattern behind the Mango Markets and Cream Finance exploits.

Additive Penalties

These fire for specific dangerous combinations or events and add directly on top of the weighted composite. Multiple conditions stack independently.

Interaction Penalties

Compound risk conditions where two signals together are worse than either alone.

Governance Behavior Penalties

On-chain governance activity that signals elevated operational risk.

State & Structural Penalties

Structural conditions that indicate elevated risk regardless of other signals.

Yield & Liquidity Trap Penalties

Conditions related to unsustainable yield or trapped capital.

Hard State Floors

These ensure a catastrophic condition can never be masked by a low smooth rating. The composite cannot go below these values when the condition is active.

Computed-but-Zeroed Signals

These are calculated and exposed in the API payload but don’t add to the weighted composite — they feed into additive penalties or are surfaced directly for consumers.

Risk Flags

Flags are surfaced in the API alongside the rating. Each maps to one or more of the conditions above.

Blocking Flags

These force a do_not_list verdict:
  • unverified
  • redemption_closed
  • dormant
  • emergency_shutdown

Non-Blocking Flags

These are informational and do not force a verdict on their own: depeg · high_looping_exposure · no_audits · eoa_owner · pause_capable · upgradeable · negative_return · lockup_7d · withdrawal_delay · low_tvl · new_vault · deposit_closed · inactive · subvault · thin_collateral_market · concentrated_borrower · concentrated_depositor · recent_upgrade · unaudited_upgrade · repeated_pausing · ownership_transfer · exchange_rate_spike · exchange_rate_crash · erc4626_donation_risk · reward_dependent_yield · yield_trap · emergency_deposit_cap · shared_collateral_exposure

Vault Risk API

Endpoints, query parameters, response format, and risk tags

Depeg Monitor

Real-time depeg risk monitoring for stablecoins and pegged assets