Klever

Track record score 91 out of 100. Public records show 100 regarding regulatory cleanliness with 0 regulatory actions, and 80 on incident history with 1 historical incident. Overall, the project’s compliance profile appears strong, and despite a past incident, the broader historical record is relatively favorable compared to most assets in the same class.

Developer health score 0 out of 100. Public software activity indicators are effectively absent: 0 GitHub stars, 0 forks, 0 commits in the last 4 weeks, and 0 PR contributors. The flagged condition norecentcommits suggests there has been no observable development momentum recently, which materially lowers confidence in ongoing maintenance and improvement.

Network security score 42 out of 100. On-chain and economic security signals are mixed. The asset scores 0 for loweconomicsecurity despite having a hard cap of 10,000,000,000 and 100% of total supply circulating. There is 1 historical incident (incident history score 75), but the overall economic security assessment remains weak, lowering the protocol’s resilience expectations.

Social and behavioral score 60 out of 100. Social audience metrics show TW (linked) with 46 and TG with 20,394. However, the sentiment flags indicate majoritynegativesentiment, and risk signals summarize 0 allegations, 1 bad press, 0 regulatory, and 1 incidents. With no snapshot available for influencer analytics, overall social safety looks moderate rather than strong.

Adoption and liquidity score 17 out of 100. Liquidity is limited: daily volume shows 24h volume of $171,330 but also very low L1 volume is flagged. Exchange listing data indicates 5 CEX listings (4 green-trust), yet the market cap tier score is 0 with market cap at $7,110,469, which aligns with thinner market depth and higher trading risk during volatility.

Inherent crypto risk (Klever). Even with decent track-record signals, Klever’s safety profile is held back by very weak developer health, low economic security, and low liquidity/volume conditions. For investors, that combination can increase the chance that performance stalls, security assumptions weaken, and price/liquidity gaps widen during stress events.