rainbow-me/rainbow

🌈‒ the Ethereum wallet that lives in your pocket

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 13 minutes ago
Added to GitGenius on September 15th, 2026
Created on March 20th, 2019
Open Issues & Pull Requests: 35 (+0)
GitHub issues: Enabled
Number of forks: 758
Total Stargazers: 4,389 (+0)
Total Subscribers: 68 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.0 days
Mean response time: 29.2 days
90th percentile: 45.5 days
Tracked items: 38

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 20 days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • stale (28)
  • no-issue-activity (2)
  • ticketed (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Rainbow is a mobile and browser extension Ethereum wallet built with React Native and TypeScript.

The wallet addresses the need for accessible self-custodial Ethereum asset management across multiple platforms. It operates as a non-custodial wallet, meaning users retain full control of their private keys and funds. The tool integrates with Ethereum networks and DeFi protocols, allowing users to manage tokens, view balances, and interact with decentralized applications directly from their mobile device or browser.

Rainbow targets individual users seeking a straightforward Ethereum wallet experience on iOS, Android, and desktop browsers. It suits those who want a single interface across multiple platforms without relying on centralized exchanges or custodial services. The project is distributed through official app stores and browser extension marketplaces, making it accessible to mainstream users rather than requiring manual compilation or deployment.

Development activity shows consistent maintenance across the codebase. The project uses pinned tool versions managed through mise to ensure reproducible builds and development environments. Setup procedures distinguish between internal developers with access to private repositories and external contributors, with the latter requiring their own API keys from third-party services like Etherscan, Infura, and Firebase. The postinstall scripts automate configuration generation and prebuild hooks, indicating attention to developer experience and build reliability. External contributors face some feature limitations due to restricted access to certain data provider APIs, which the maintainers acknowledge as an ongoing constraint they are working to resolve.