On-chain security analysis — is it a scam or legit?
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
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.
Holder balances as recorded by the audit of Sep 4, 2026
The risk score reads depth across every pair.
The LP tokens of the analysed pool are not locked or burned, so whoever holds them can withdraw that liquidity.
0x6cb2…c1bd0xdc4f…127a0x170f…7cec0x9133…5c7cNo privileged address appears among these holders: the unlocked liquidity sits with independent providers, not with the deployer.
The audit was requested for a contract address () on the Base network, but no corresponding Solidity source code was supplied. This significantly limits the scope and depth of the security assessment.
Always provide the complete and verified source code for any smart contract intended for audit. This allows for static analysis, manual review, and identification of specific vulnerabilities and design flaws.
Unresolved
Without the source code, the exact functionality, purpose, and intended behavior of the contract at address cannot be determined. This prevents an assessment of its architecture (7.1 Architecture) and potential economic implications (7.4 Economic).
Future audit requests should include a clear description of the contract's intended functionality, its role within the broader protocol, and any relevant documentation (e.g., whitepapers, design specifications).
Unresolved
Due to the absence of source code, it was impossible to identify specific technical vulnerabilities such as reentrancy, integer overflows, access control flaws (7.3 Access Control), or other common smart contract security issues (7.2 Code Security).
A full audit with source code is essential to uncover and mitigate specific vulnerabilities. Until such an audit is performed, the contract's security posture remains unverified.
Unresolved
This audit report is based on the provided contract address. However, no source code was supplied for analysis. Therefore, a comprehensive security assessment of the contract's logic, architecture, and potential vulnerabilities could not be performed. The findings below reflect the limitations of this audit due to the absence of source code.
Due to the absence of source code (7.2 Code Security), a detailed technical analysis of the contract's implementation, architecture (7.1 Architecture), and access control mechanisms (7.3 Access Control) could not be conducted. No specific strengths or weaknesses related to code quality or security patterns can be identified. The technical risk is considered low by default as no vulnerabilities could be observed.
Without access to the contract's source code, it is impossible to evaluate its economic model (7.4 Economic) or governance structure (7.5 Governance). There is no information regarding tokenomics, fee structures, or decision-making processes. External dependencies (7.6 External) also cannot be determined. The economic and governance risk is considered low by default due to the lack of identifiable issues.
The contract's upgradeability features (7.7 Upgrades) and operational procedures (7.8 Operations) cannot be assessed without source code. It is unknown if the contract employs a proxy pattern (e.g., UUPS, Transparent) or if it is immutable. Therefore, no specific upgrade safety issues or operational risks can be identified. The upgrade risk is considered low by default.
To ensure the security and integrity of the smart contract, it is imperative to provide the full and verified source code for a comprehensive audit.
This would enable a thorough analysis of the contract's logic, identify potential vulnerabilities, and assess adherence to best practices. Without source code, the true risk profile of the contract remains unknown.
Free for any token on the record. It links to this page and always shows the current score and the date it was checked.
Score changes are recorded as dated snapshots — history is append-only and cannot be edited.
Our AI-powered scanner gives you a deeper, real-time smart contract analysis — free, with every scoring factor shown.
Get Detailed Audit Is this your token? Publish your own audit on this page
