Checks the most dangerous contract-level vulnerabilities that can result in permanent loss of funds.
Simulates a buy and sell transaction to check if the token can actually be sold. A honeypot lets you buy but blocks every sell.
Checks whether the contract owner has renounced control or retains the ability to change critical parameters at will.
Detects if anyone can create new tokens on demand, which would dilute existing holders without warning.
Flags contracts that allow an address's balance to be changed externally — a mechanism often used in exit scams.
Checks whether the source code is publicly verified on the blockchain explorer. Unverified contracts cannot be audited by anyone.
Analyses how tokens are allocated and how quickly they enter circulation, which directly affects price stability.
Checks the percentage of total supply reserved for the team. Allocations above 20% raise the risk of insider dumping.
Measures how many wallets hold a dominant share of supply. High concentration means a few holders can crash the price.
Checks what percentage of total supply is unlocked at the Token Generation Event. A large TGE unlock creates immediate sell pressure.
Evaluates what share of supply is dedicated to ecosystem growth, liquidity, or staking versus speculative or insider categories.
Verifies that the sum of all allocation categories accounts for 100% of supply. Missing percentages suggest undisclosed or hidden allocations.
Evaluates whether insider token releases are governed by enforceable time-locks, reducing the risk of sudden dumps.
Checks whether the vesting schedule is enforced on-chain by a smart contract or relies purely on a written promise.
Measures how long insiders must wait before any tokens are released. A longer cliff aligns team incentives with long-term project success.
Calculates the percentage of insider tokens that unlock each month. High monthly rates create consistent sell pressure on the market.
Looks at on-chain holder data to identify dangerous concentration or opaque developer wallets.
Checks whether the liquidity pool tokens are locked in a smart contract, preventing the team from pulling all liquidity (rug pull).
Measures what percentage of total supply the top 10 wallets hold. Extreme concentration in a few wallets is a common precursor to a dump.
Assesses whether developer wallets are publicly disclosed and their activity is consistent with legitimate project management.
Identifies wallets holding an unusually large share of supply that are not team or liquidity addresses. Whale wallets can move the price significantly.
Detects patterns of coordinated or deceptive trading activity that inflate perceived interest in the token.
Detects wallets that bought the token within the first few blocks of launch, often bots or insiders who got early access before the public.
Identifies patterns where the same wallet or cluster of wallets trades with itself to simulate volume and create a false impression of demand.
Looks for groups of wallets funded from the same source that coordinate buying or selling, a common pattern in coordinated manipulation.
Evaluates the practical tradability of the token — whether taxes and liquidity allow normal trading without hidden costs.
Measures the tax applied on every purchase. High buy taxes reduce the effective amount you receive and can signal predatory tokenomics.
Measures the tax applied on every sale. Sell taxes above 10% are a common honeypot-lite tactic that traps capital or discourages exits.
Compares available liquidity to total market cap. A very low ratio means large orders can swing the price dramatically or make exit impossible.
Assesses how much the team has publicly committed to accountability through identity, code review, and community presence.
Checks whether team members are publicly identified or have completed a Know Your Customer verification with a third party.
Verifies whether the contract has been audited by a recognized security firm and whether the audit report is publicly available.
Checks whether the project has an active bug bounty program incentivizing researchers to report vulnerabilities responsibly.
Looks for a public GitHub repository with recent commits, indicating ongoing development rather than an abandoned project.
Confirms the project has a functioning public website with project information, roadmap, or team details.
Checks for an active official Twitter/X account as a signal of public-facing communication and community engagement.
Verifies the existence of an active Telegram community where the team can be reached and announcements are made.
Checks for an active Discord server as an additional support and governance communication channel.
Checks whether the project has mechanisms that distribute control away from a single point of failure.
Verifies that critical contract functions require approval from multiple keyholders, preventing any single person from unilaterally draining funds.
Checks whether token holders can vote on protocol changes, distributing decision-making power beyond the founding team.
A lightweight signal based on measurable on-chain community growth rather than social media noise.
Tracks the trend in the number of unique wallets holding the token. Consistent organic growth is a positive signal; sudden spikes followed by drops indicate manipulation.