Skip to content
Crypto Almanac Daily
R
Wallets

Rabby

Best for open-source verification

Source code:Public repositoryDocumentation:OpenSecurity page:Not identifiedPublisher:DeBankRubric:v2.0 · verified 9 Aug 2026
Last verified August 9, 2026
Confidence BRubric v2.0Verified August 9, 2026
8.0
out of 10
Open account
Scorecard

How it rates

Key custody & openness · 35%10.0
Cost transparency · 5%8.0
Product openness · 25%8.0
Publisher transparency · 20%6.0
Public documentation surface · 15%6.0
Pros
  • Source published in a public repository
  • Documentation open without an account
Cons
  • No dedicated security page identified at this check
  • Terms not found at the conventional address at this check
How this score was built

Each indicator scores 2, 1 or 0. A pillar is the points earned over the points available; the overall score is the weighted sum. Every source below is public — check any of them yourself.

Key custody & openness · 35% weight10/10 points · 10.0/10
  • Met
    Source code published in a public repository

    Repository reachable at this check.

    github.com/RabbyHub/Rabby
  • Met
    Security documentation or disclosure page published

    Security or support documentation reachable.

    rabby.io/docs
  • Met
    User documentation reachable without an account

    Documentation open at this check.

    rabby.io/docs
  • Met
    Publisher identifiable from its own repository organisation

    Repository published under DeBank.

    github.com/RabbyHub/Rabby
  • Met
    Product site reachable for independent verification

    HTTP 2xx at this check.

    rabby.io/
Cost transparency · 5% weight8/10 points · 8.0/10
  • Met
    Product site public

    Reachable at this check.

    rabby.io/
  • Not met
    Terms or legal documentation public

    Not found at the conventional address at this check.

  • Met
    Documentation states how the product is funded or priced

    Documentation available to check.

    rabby.io/docs
  • Met
    No account required to read product information

    No account required at this check.

    rabby.io/
  • Met
    Support resource public

    Reachable at this check.

    rabby.io/docs
Product openness · 25% weight8/10 points · 8.0/10
Publisher transparency · 20% weight6/10 points · 6.0/10
  • Met
    Publisher entity identifiable

    Identifiable as DeBank.

    github.com/RabbyHub/Rabby
  • Met
    Site resolves to automated verification

    HTTP 2xx at this check.

    rabby.io/
  • Not met
    Security or disclosure page published

    Not identified at this check.

  • Not met
    Terms or legal documentation published

    Not found at the conventional address at this check.

  • Met
    Support or help resource published

    Reachable at this check.

    rabby.io/docs
Public documentation surface · 15% weight6/10 points · 6.0/10
  • Met
    Product site reachable

    HTTP 2xx at this check.

    rabby.io/
  • Met
    Documentation reachable

    HTTP 2xx at this check.

    rabby.io/docs
  • Met
    Public repository reachable

    HTTP 2xx at this check.

    github.com/RabbyHub/Rabby
  • Not met
    Security page reachable

    Not identified.

  • Not met
    Legal documentation reachable

    Not found at the conventional address.

An open-source EVM wallet that simulates each transaction and shows the resulting balance changes and approvals before you sign.

Our assessment

Rabby is an open-source EVM wallet built by DeBank whose defining feature is that it tells you what a transaction will actually do before you sign it. It simulates the call, shows the resulting balance changes and token approvals, flags risk, and switches networks automatically to match the dapp.

Simulation is the answer to signature phishing

The dominant way people lose money in DeFi is approving something they did not understand — a blind signature, an unlimited approval, a drainer contract. Rabby built pre-execution simulation and risk scanning early, and reported comparisons put its simulation accuracy and malicious-transaction detection ahead of the incumbent. Whether the exact figures hold, the design premise is correct: an interface that shows outcomes beats one that shows hex.

Approval management built in

Old token approvals are a standing liability — a contract you authorised in 2021 can still drain a token in 2026. Rabby exposes and revokes approvals inside the wallet rather than requiring a separate tool, which means people actually do it.

Where the evidence is thin

Source is public under the vendor organisation and documentation is reachable, but we found no security disclosure page or legal terms at conventional addresses. For a wallet whose pitch is safety, a published vulnerability-reporting channel is a conspicuous omission.

Who it suits

Rabby fits active DeFi users on EVM chains who sign a lot of contract interactions and want to see the consequences first. Users who need non-EVM chains should pair it with Phantom or Keplr; those who value maximum dapp compatibility above all will stay on MetaMask.

Alternatives

How rivals compare

ServiceScoreBest for
Trust Wallet9.9open-source verificationRead →
MetaMask9.9open-source verificationRead →
Reference

Frequently asked

Does this score mean Rabby is safe?

No. It measures what a user can verify before installing: published source, documented security posture, open documentation and an identifiable publisher. Runtime key handling is not tested by us.

Why does open source matter for a wallet?

It is the one substantive property an outsider can check without reverse-engineering the app. Everything else requires trusting the publisher or a third-party audit.

What would raise this score?

Publishing source, a dedicated security page, open documentation and terms at stable public addresses — all checkable by anyone.