Early-stage security check — honeypot & rug-pull analysis
0xfe67…f6b3
This report is based on a security audit of the contract at 0xfe67d6f5adbacf718f7ce0328a8c7e43bba5f6b3. No source code was provided for analysis, therefore a comprehensive security assessment could not be performed. The risk levels and findings reflect the absence of code rather than an actual analysis of the contract's logic.
Share held by contracts — treasury, vesting, bridge or staking — is discounted against share held by wallets when the score is computed: a contract cannot decide to sell the way an anonymous holder can, though it can still be drained or voted to sell. Effective concentration is the figure the risk score is actually calculated from.
The risk score reads depth across every pair. The volume figure and the volume-to-liquidity ratio elsewhere on this page describe only the pair this audit analysed, so the two are not directly comparable.
0xbc51…108a0x52e5…45b40x1d2a…158cNo privileged address appears among these holders: the unlocked liquidity sits with independent providers, not with the deployer.
Each factor is an on-chain fact recorded at the time of this analysis. The score is computed from them by a deterministic function, so the same contract returns the same score for anyone who runs the audit. How scores are computed
This token is brand new. Run a deeper AI-powered analysis of the contract code — free and instant.
Get Detailed Audit