Contract safety measurements on Base, fetched live and rendered server-side. Each row names the endpoint it came from so you can check it yourself.
0xe62bfbe57763ec24c0f130426f34dbce11fc5b06 ยท view on Base explorer
| Check | Value | Source |
|---|---|---|
| Honeypot simulation ran | NO | api.honeypot.is/v2/IsHoneypot (chainID=8453) |
| Holders | 3,591 | api.honeypot.is/v2/IsHoneypot (chainID=8453) |
| GoPlus | unreachable: no record for this address | api.gopluslabs.io/api/v1/token_security/8453 |
The honeypot simulation could not run against this token. That usually means there is no meaningful liquidity to trade against yet โ which is precisely the presale window where most losses happen. Treat "no honeypot detected" here as NO INFORMATION, not as good news.
GoPlus has no security record for this address on this chain. Very new contracts often have none for a while. Absence of a record is absence of data, not a clean bill.
No LP holder data was returned, so nothing can be said about whether liquidity is locked or burned.
This page states measurements, not a verdict. There is no score here on purpose: a number with its source beside it is something you can verify, and a score is something you have to trust. Checking many tokens at once? The same checks run as an API at Base Token Risk Scanner.