FORESHOCK

Protocols

Request coverage

Only protocols with enough independently verified data to trust a score appear here. This is a permanent rule, not a temporary gap.

Coverage grows three ways: protocols Foreshock selects at its own discretion, protocols requested through the Request coverage button, and sponsored assessments delivered on an agreed timeline. No path has a guaranteed date except sponsorship.

Jupiter Lend

Solana

medium:

  • Backtest coverage is limited.
  • Only 3 comparable incidents or controls were found in this protocol's TVL, age, and category bucket.
  • 80% of category weight is verified data.
Why this rating
Every category's contribution to the overall score, highest first.
Dependency risk10.6Verified

Uses 4 oracles (four independent oracle providers combined via a hop-based architecture that chains up to four sources sequentially (e.g. JUPSOL/SOL derived by chaining JUPSOL/USD and SOL/USD), reducing dependency on any single source; freshness validated at 600 seconds for user operations and 7200 seconds for liquidations, plus Pyth confidence-interval checks).

Audit profile10.0Verified

1 audit/contest on record, most recent (Code4rena, 2026-07-10) has unread findings, scored as unknown, not assumed clean.

Code characteristics6.8Verified

Admin key: timelock, upgradeable without a meaningful timelock, open source.

Governance attack surface5.0Unverified

No verified evidence yet; held at the neutral midpoint rather than assumed safe or unsafe.

TVL profile3.5Verified

TVL change (14%) is within a stable range.

Protocol age2.8Verified

346 days live, still young.

Team factors2.5Unverified

No verified evidence yet; held at the neutral midpoint rather than assumed safe or unsafe.

Bug bounty2.5Unverified

No verified evidence yet; held at the neutral midpoint rather than assumed safe or unsafe.

Historical incidents2.3Verified

No known own or inherited incidents.

Dependencies (1)

Uses 4 oracles (four independent oracle providers combined via a hop-based architecture that chains up to four sources sequentially (e.g. JUPSOL/SOL derived by chaining JUPSOL/USD and SOL/USD), reducing dependency on any single source; freshness validated at 600 seconds for user operations and 7200 seconds for liquidations, plus Pyth confidence-interval checks).

Incident history (0)

No material incidents on record.

Audit history (0)

No audit history recorded.

This assessment follows Foreshock's published methodology. Exact category weights, scoring rules, thresholds, and aggregation logic are proprietary and not shown here. How to interpret this assessment

Do you hold a position in this protocol?

Get an email when this assessment materially changes.