Early-stage security check — honeypot & rug-pull analysis
SolanaAutomated review assessed the protocol architecture, upgrade controls, and external dependencies based on available inputs.
Read the full analysisEach 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
How the supply is spread across holders could not be read — the indexer's holder list does not add up to the supply. Check the largest holders on a block explorer, which reads current balances.
The risk score reads depth across every pair.
The LP tokens of the analysed pool are locked or burned.
Liquidity $9K (DexScreener, all pools). 24h trading volume $162K (DexScreener, all pools).
Size any position to the liquidity and daily volume shown — they set how much you can sell and at what price.
Acknowledged
This token is an SPL token mint, not a deployed program: there is no contract source code on-chain for a line-by-line review, so no code-level vulnerability could be identified either way. The assessment on this page therefore rests on mint/owner authority, mint capability, LP lock/burn state, which are read directly from chain state and from third-party risk registries.
Read the risk score breakdown below as the substance of this audit. For a code-level review, the token would need an accompanying verified program.
Acknowledged
Not listed by CoinGecko or any exchange GoPlus tracks. Nothing independent confirms who is behind this token, so every power its contract grants is scored at face value.
Match the contract address against the project's official channels before trading.
Acknowledged
100.0% of the pool's LP is burned or time-locked. 100.0% of the pool's LP tokens are burned — that liquidity can never be withdrawn by anyone.
Check the lock's end date and beneficiary on the locker's own page before relying on it.
Acknowledged
A community token whose value comes from attention rather than a product. Being a meme is not a risk in itself: it is scored on exactly the same contract and market facts as any other token. The class itself adds no points; the contract and market facts decide the score. Basis: launched on pump.fun, a meme launchpad. Tokenomics — Supply: fixed — the contract has no mint function. Control: nobody (ownership renounced). Code: not upgradeable (no proxy). Fees: no buy or sell tax. Market: $9K of DEX liquidity across 2 pools. Launch: launched on pump.fun, under a day of market history.
Expect attention-driven volatility; the facts in this report say whether the contract itself can be used against holders.
Acknowledged
The token's oldest DEX pool is less than a day old. Age is not part of the risk score — a new token is not a risky one by default — but a short history means fewer trades and holder changes behind the facts in this report.
Re-check ownership, liquidity and holder distribution as the token matures; those are the facts that move early.
Acknowledged
Automated review assessed the protocol architecture, upgrade controls, and external dependencies based on available inputs. Core flows look consistent and follow common patterns, but some edge cases and monitoring gaps remain. This report balances strengths with concrete remediation steps to reduce risk before deployment.
Architecture (7.1) is modular, separating storage, strategy, and interface layers to contain faults and align with standards like ERC-20. Code security (7.2) is mostly solid with input validation and checked arithmetic, yet some low-level calls lack explicit success checks. Access control (7.3) applies role-based modifiers to critical paths, but owner actions are not consistently protected by timelocks or pausing. Example: a guarded withdraw flow blocks reentrancy, while unguarded emergency exits could be abused during market stress.
Economic design (7.4) uses capped emissions and fee ceilings, and rate limits reduce flash-loan sensitivity. However, reward curves still depend on liquidity timing, and unbounded parameter changes could amplify slippage or dilution. Governance controls (7.5) rely on a multisig with role separation, but there is no on-chain timelock for treasury redirects or fee changes. External dependencies (7.6) rely on oracles and third-party calls with sanity bounds, yet fallback behavior during oracle outages should be documented to prevent DoS.
Upgrade lifecycle (7.7) follows proxy standards and initializer versioning, which reduces accidental state resets. Still, upgrades can be executed without delay and rollback testing is limited, increasing operational risk. Operational readiness (7.8) benefits from monitoring hooks and clear runbooks, but emergency pause playbooks should be rehearsed. Example: add a time-delayed upgrade queue and rehearse recovery on testnet before mainnet changes.
Proceed with deployment after addressing high-severity findings and adding timelock protections for admin actions.
A short remediation sprint for medium issues will materially reduce upgrade and oracle risk.
This token is brand new. Run a deeper AI-powered analysis of the contract code — free and instant.
Get Detailed Audit Is this your token? Publish your own audit on this page
