Beam

Track record score 100 out of 100. Public records show a clean regulatory history with 0 regulatory action(s) and no historical incidents on record (incident clean score 100). This gives the asset the strongest possible background signal, suggesting there are no known compliance or major event red flags tied to prior activity.

Developer health score 0 out of 100. The project currently shows 0 GitHub stars, 0 forks, 0 commits in the last 4 weeks, and 0 PR contributors, alongside the flag indicating no recent commits. Combined, these signals point to very low or inactive measurable development activity over the observed window, which reduces confidence in near-term engineering momentum.

Network security score 59 out of 100. On-chain and protocol-related checks show 0 historical incidents on record (incident history 100) and a defined hard cap of 58,470,184,687 (supply cap defined 100). Circulation is relatively healthy at 88% circulating (circulating ratio 80), but economic security is weaker at 22 given the market-cap context ($103,108,694). Overall, it’s mid-range: fewer incident signals, but limited economic robustness.

Social and behavioral risk score 76 out of 100. Social audience data shows Twitter (linked) with an unavailable follower count and Telegram at 4,720. Sentiment is strongly positive with 100% up and 0% down, and risk checks report 0 allegations, 0 bad press, 0 regulatory flags, and 0 incidents. One enrichment record is unavailable, but the captured signals are generally orderly.

Adoption and liquidity score 44 out of 100. Trading and market access look mixed: 24h volume is $6,222,999 (daily volume score 20), while exchange listing breadth is high with 62 CEX listings (100) and 29 green-trust. However, the market-cap tier score is 0 for this asset at $103,108,694, which pulls the bucket lower. Liquidity appears present, but not consistently deep relative to demand.

Even with a mid-grade safety score, crypto assets inherently carry risk: liquidity can fluctuate, protocol economics can change, and development activity can affect long-term viability. For Beam specifically, the biggest practical concern from the provided data is the lack of measurable recent commits, while security indicators show few or no incident records and a defined supply cap.