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.
0x1a44233fae8d50f1aeb3a5d58dd426ff4814cb53 · view on Base explorer
| Check | Value | Source |
|---|---|---|
| Honeypot simulation ran | yes | api.honeypot.is/v2/IsHoneypot (chainID=8453) |
| Flagged as honeypot | no | api.honeypot.is/v2/IsHoneypot (chainID=8453) |
| Buy tax | 0% | api.honeypot.is/v2/IsHoneypot (chainID=8453) |
| Sell tax | 0% | api.honeypot.is/v2/IsHoneypot (chainID=8453) |
| Transfer tax | 0% | api.honeypot.is/v2/IsHoneypot (chainID=8453) |
| Holders | 6,449 | api.honeypot.is/v2/IsHoneypot (chainID=8453) |
| GoPlus | unreachable: no record for this address | api.gopluslabs.io/api/v1/token_security/8453 |
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.