FORESHOCK

Protocols

Request coverage

Every protocol here carries a dated score and the share of it backed by independently verified evidence. Where that share is still thin the assessment says so, is marked Low-signal rather than given a risk band, and holds every unevidenced category at the neutral midpoint instead of assuming it safe. Every score and its reasoning are free to read; the underlying dependency, incident and audit records are part of a plan. Each reading here is fixed at the date beside it. Re-scoring never stops, but a changed reading reaches plan holders on the day it changes rather than this page, which is what a plan is for. How a score is built, how to read one, and how the rubric was tested against real exploits are all in the methodology.

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.

Scores run from 0, the safest reading, to 100, the riskiest, where 50 is the neutral midpoint every unverified category is held at. Red marks a protocol scoring 50 or above, the band called Elevated: worse than neutral on the evidence gathered. Amber marks one below it, called Moderate. The boundary is fixed. It does not move as coverage grows, and it is not fitted to any backtest result.

PancakeSwap AMM V3

PancakeSwap AMM V3 official site N/A

Multi-Chain

:

  • Evidence: this reading is based on 100% of the scored weight, verified against named sources. Categories without verified data are held at the neutral midpoint at their full weight, never counted as safe.
  • Validation: measured against 1 comparable incident/control in this protocol's TVL, age and category bucket.

Published 2026-09-25. Up-to-date reading and 2 changes since for subscribers. See plans

Why this rating
Audit profile10.0
4 audits on record, most recent audit is over 2 years old; the most recent audit found 0 High and 2 Medium severity issues. This reflects code quality at the time of that audit only, not a claim that these specific issues are still unresolved today.
Code characteristics9.0
Admin key: an unidentified controlling contract (no single key can act alone; its signers and any delay are unverified), open source.
Governance attack surface5.0
Governance concentration/quorum data unknown.
Dependency risk3.8
No bridge or oracle dependencies on record, composable with 1 other protocol. PancakeSwap V3's AMM core has NO external price-oracle dependency, and this was verified in the source rather than inferred: PancakeV3Pool.sol's complete external import list is its own libraries plus one PancakeSwap package, IPancakeV3LmPool, with no Chainlink, Pyth, Band or any other feed anywhere.
Show the evidenceThe direction is the reverse: each pool holds a 65 535-slot observations array and its own Oracle library describes itself as providing 'price and liquidity data useful for a wide variety of system designs', with an OracleLibrary consult() helper in the periphery offered TO integrators returning arithmeticMeanTick and harmonicMeanLiquidity. So the correct dependency framing is downstream, not upstream: the risk sits with protocols relying on V3 TWAPs, not with V3. One cross-chain dependency exists and it belongs to the TOKEN, not to the AMM: CAKE 'uses LayerZero v1 OFT standard to bridge across chains' with BSC as the canonical chain, corroborated by separate audits of the CAKE bridge on PancakeSwap's own registry. V3 pools on each chain are independent deployments with no cross-chain messaging between them, so LayerZero must not be recorded as an AMM dependency.
TVL profile3.5
TVL change (11%) is within a stable range.
Team factors3.0
Anonymous team, a weak but real signal on its own.
Historical incidents2.3
No known own or inherited incidents as of 25 September 2026.
Protocol age1.5
1271 days live, past the ~1yr floor; treated the same as any older protocol, not scored progressively safer with more age.
Bug bounty0.7
Has a bug bounty program, up to $1 000 000, hosted on Immunefi.
Assets held (0)

No per-symbol breakdown of this protocol's value is published, so there is nothing to read here and nothing has been researched. For an exchange or a bridge this is usually a fact about the protocol rather than a gap: value sits in many user positions rather than in a held set of assets.

Dependencies (2)

Available with a plan. See pricing.

Incident history (0)

Available with a plan. See pricing.

Audit history (4)

Available with a plan. See pricing.

Common questions about PancakeSwap AMM V3

Foreshock's independent reading of PancakeSwap AMM V3 is Moderate risk, 38.8 out of 100, as of 25 September 2026. The largest single contributor to that reading is audit profile: 4 audits on record, most recent audit is over 2 years old; the most recent audit found 0 High and 2 Medium severity issues. This reflects code quality at the time of that audit only, not a claim that these specific issues are still unresolved today. All nine scored categories are backed by verified evidence. This published reading is fixed at that date. Re-scoring never stops, and when a reading changes it reaches plan holders on the day it changes rather than this page. Foreshock publishes the reading and the reasoning behind it. It is not a verdict on whether to use this protocol, and it is not investment advice.

Is PancakeSwap AMM V3 safe?
Foreshock does not answer that as a yes or a no. Its independent reading of PancakeSwap AMM V3 is Moderate risk, 38.8 out of 100, as of 25 September 2026, led by audit profile: 4 audits on record, most recent audit is over 2 years old; the most recent audit found 0 High and 2 Medium severity issues. This reflects code quality at the time of that audit only, not a claim that these specific issues are still unresolved today. The score and the reasoning are published in full so the reading can be checked rather than trusted.
Has PancakeSwap AMM V3 been audited?
4 audits on record, most recent audit is over 2 years old; the most recent audit found 0 High and 2 Medium severity issues. This reflects code quality at the time of that audit only, not a claim that these specific issues are still unresolved today. An audit describes the code at the time it was reviewed. It is not a statement that the protocol is safe today.
Who controls PancakeSwap AMM V3?
Admin key: an unidentified controlling contract (no single key can act alone; its signers and any delay are unverified), open source. Governance concentration/quorum data unknown.
Has PancakeSwap AMM V3 been exploited before?
No known own or inherited incidents as of 25 September 2026. Foreshock records an incident against a protocol whether it originated there or was inherited from something it depends on.
When was this PancakeSwap AMM V3 assessment last updated?
25 September 2026, and that date does not move on its own. A reading published here is fixed when it is published; re-scoring never stops, and a changed reading reaches plan holders on the day it changes rather than this page. Every category carries the date of the evidence behind it.
Also covered on Multi-Chain

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

This reading will change.

This reading is fixed at the date above it, and it stays there. We keep re-scoring PancakeSwap AMM V3 as the evidence moves, a new audit, a changed admin control, an incident, and this page is free to read and always will be. The updated reading is what a plan buys: you are told by email on the day it changes, instead of finding out the next time you happen to look.

Pick one protocol and get a free weekly summary of what changed. Same-day alerts come with a plan.

Monitor this protocolGet told when this changesBrowse every protocol