Why permissions matter
Honeypot detection answers an important transaction question, but it does not by itself answer whether a contract can mint new supply, change behavior, or expose privileged controls. Contract-control signals belong beside liquidity and concentration, not in isolation.
What Jepeta checks
MintabilityShown in the public preview when available. Mintability can materially change supply assumptions.
Dangerous permissionsIncluded in the paid evidence report when supported by the upstream contract-security data.
Honeypot signalCan independently trigger a BLOCK; a non-honeypot result is not treated as proof of safety.
TaxesBuy and sell tax context when reported by the security source.
Market contextMatching Base liquidity, observed concentration and LP-lock context help show how contract risk meets execution risk.
A practical pre-trade sequence
- Use the exact token contract address.
- Check honeypot and mintability first.
- Review liquidity and holder concentration instead of stopping at the contract signal.
- For material WARN/BLOCK cases, inspect the Full Report's evidence before deciding what your own policy allows.
Do not reduce this to one flag. “Not mintable” is not a safety guarantee. “Mintable” is not automatically malicious. The useful question is what the observed permission means in combination with the rest of the token's current evidence.