Kite

Track record score 91 out of 100. Public records show regulatory cleanliness at 100 with 0 regulatory actions and an incident-clean history at 100 with 0 historical incidents. Research did raise 2 additional concern(s), reflected in agent red flags scoring 30, which is the main offset despite the strong clean record. Overall, the project’s historical compliance and incident profile look strong relative to many peers.

Developer health score 0 out of 100. GitHub-derived measures show 0 stars, 0 forks, 0 commits in the last 4 weeks, and 0 PR contributors, with the additional flag "norecentcommits". This points to extremely limited observed development activity in the most recent window, which is a major safety concern for a protocol expected to iterate and address risks over time.

Network security score 61 out of 100. Economic security is constrained at 34 given a market cap of $386,974,557, and circulating supply is under half at 23% (flag: "under50pctcirculating"), scored 30. However, incident history is clean at 100 with 0 historical incidents on record and a hard cap is defined at 10,000,000,000 (scored 100), which supports predictable supply conditions.

Social and behavioral score 69 out of 100. Audience signals show TW (linked) and TG (linked) with social_audience scoring 25, while sentiment is positive at 80% up versus 20% down. Research-based behavioral risk signals are strong at 100 with 0 allegations, 0 bad press, 0 regulatory issues, and 0 incidents, though there is also a note that enrichment record data is unavailable, limiting how deeply some signals can be verified.

Adoption and liquidity score 50 out of 100. Daily activity is moderate with $50,415,666 in 24h volume (score 43), and exchange listing coverage is strong at 41 CEX listings with 25 marked as green-trust (score 94). Market cap tier scoring is 0 for the current market cap of $386,974,557, and this mismatch contributes to the middling overall liquidity and adoption assessment.

Inherent crypto risk note for Kite (L1 protocol): Even with a solid historical compliance and incident record, the asset still carries typical protocol and market risks. The biggest specific risks here are extremely weak observed developer activity in the last month and economic constraints driven by limited circulating supply relative to total supply, which can affect liquidity dynamics and security responsiveness.