Early-stage security check — honeypot & rug-pull analysis
0xcc5f…32bb
This report is based on a limited analysis as no Solidity source code was provided for the contract at 0xcc5f65809fef01bfb7270345f993f19771b132bb. Without the source code, a comprehensive security audit for vulnerabilities, architectural design, and economic implications cannot be performed. The findings below are general best practices and an acknowledgment of the missing information.
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.
0xed16…10e10x1d2a…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