Public score as of Nov 7, 7 days behind. Live subscribers see every move the moment it lands.
Go live for $29
Revert Stableswap
Score history
Model updateEvery Score Move
Live for subscribersOpen any move to see what changedMay 15up 1Model updateDimensions rescored
BlackHart's method or evidence changed and the score was recalculated. No new release drove this move.
Dimensions
12 dimensions, 11 apply to Revert Stableswap. Open one to see how it is scored.Access controlscore 62weight 19%
Admin keys, roles, permissions and the checks that guard them.
Economic soundnessscore 45weight 14%
How the economic design holds up under flash loans, MEV, liquidation cascades and bad incentives.
Oracle integrityscore 55weight 14%
How prices reach the protocol, and how hard they are to manipulate or let go stale.
Maturityscore 35weight 13%
Time in production, value secured over time, audits, bounties and incident history.
- Live since
- Not yet measured
- TVL
- Not yet measured
- Audits
- Not yet measured
- Bug bounty
- Not yet measured
Governancescore 60weight 11%
Admin key concentration, timelocks and how upgrades happen.
Adversarial resiliencescore 35weight 7%
How the code holds up under independent adversarial research.
Compositional riskscore 50weight 5%
External dependencies and the surface where contracts and integrations interact.
Supply chainscore 65weight 4%
Compiler versions, libraries, build reproducibility and proxy patterns.
- Dependabot
- No
Cross-chain messagingscore 90weight 4%
Bridge trust model, sequencer risk, fraud proofs and replay risk.
Liquidity and market structurescore 50weight 2%
Liquidation cascades, holder concentration and exit queues, where positions trade.
Operational securityscore 62weight 2%
Incident response, deployment hygiene, key management and monitoring.
- GitHub scan
- revert-finance/stableswap-hooks on May 20
- Branch protection
- No
- Required reviews
- 0
- Signing ratio
- 52%
- Commits in 90 days
- 18
- PR review ratio
- 73%
- Has CI
- Yes
- CI success rate
- 100%
- Security policy
- No
- Deployment hygiene
- 85 of 100
- Development practices
- 39 of 100
- Emergency history
- 75 of 100
- Incident response
- 50 of 100
- Key management
- 70 of 100
- Monitoring
- 70 of 100