Each finding describes a specific feature. It is not a safety score or a guarantee of future availability.
The researcher saw this result in the public interface or repository. The finding explains the scope.
The project describes this capability. Execution was not independently confirmed.
A concrete limitation, unavailable dependency or incomplete implementation was documented.
The scenario was outside this review, often because it required an account, wallet or payment.
Research snapshot: 14 Nov 2026. Market caps: 05:35 UTC, from the first 200 entries of Pons Active. Ten product projects were selected from 16 tokens above $10k.
Automatic checks record public HTML responses, GitHub commits/releases and token-contract reads. The first successful response creates a baseline, not a change. Page/contract differences need two matching checks; GitHub changes use published identifiers. Failed requests preserve the last successful value. Live market data is fetched separately from Pons. Volume estimates use 5-minute quote-volume buckets and the current pair-asset USD rate; price changes use the pair asset. Tokens younger than 24 hours show since-launch change. Source coverage measures readable materials only. Product validation separately records dated sample or interface observations. Reading source code does not establish execution. Claims remain team statements unless a specific recorded observation supports them. Background updates preserve manual review dates. Share links freeze a saved version; Compare checks shows differences between real saved runs. X samples do not establish the full account history. Manual product conclusions are not automatically rewritten. Watchlist, notes and read marks stay in this browser; source history is stored on the server.