Free above: contract permissions, sell test and tax when data is available.
Paid report: pool balances, trading activity, large holders and estimated price impact for supported pools.
| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | Yes | Transfer simulation | 18 Nov 2026 |
| Buy tax | 0% | Contract | 18 Nov 2026 |
| Sell tax | 0% | Contract | 18 Nov 2026 |
| Admin mint | Not present | Contract | 18 Nov 2026 |
| Transfers pausable | Not present | Contract | 18 Nov 2026 |
| Address blacklist | Not present | Contract | 18 Nov 2026 |
| Upgradeable proxy | No | Contract | 18 Nov 2026 |
| Source verified | Yes | Block explorer | 18 Nov 2026 |
| Top-10 holders | 71.3% | Holder distribution | 18 Nov 2026 |
| Liquidity locked | No | LP holders | 18 Nov 2026 |
| Holders | 9461 | Token contract | 18 Nov 2026 |
| Deployed by | 0x3cc20e…107505 |
| Current owner | None — ownership renounced |
| Holders | 9,461 |
| Rank | Address | Share |
|---|---|---|
| #1 · contract | 0x5de5a5…a7cfd1 | 49.10% |
| #2 | 0x655021…be159f | 3.49% |
| #3 | 0xa2f36e…5fdbe4 | 3.32% |
| #4 | 0x78e503…8eb7ad | 2.68% |
| #5 | 0x7caf12…51ce89 | 2.68% |
This automated check of the JACKET contract on BSC scored 13 out of 18, which reflects a mix of reassuring and concerning signals rather than a simple pass or fail. On the positive side, no honeypot behaviour was detected: simulated transfers show the token can be sold, and both buy and sell tax are set to 0%, meaning the contract code does not currently route a cut of trades elsewhere. No minting function was found, so the owner does not appear able to create new tokens and dilute holders at will. No pause function was detected, so the owner does not appear able to freeze transfers for everyone. No blacklist function was found, so the owner does not appear able to block specific wallets from trading. The contract is also not an upgradeable proxy, meaning its logic cannot be silently swapped out later, and the source code is verified on the block explorer, so anyone can read exactly what it does. The two flags working against the score are that liquidity is not locked, meaning whoever controls the liquidity pool could withdraw it and leave buyers unable to trade at a fair price, and that the top 10 holders control 71.3% of supply, which means a small number of wallets could sell in a way that moves the price sharply for everyone else.
It's important to be clear about what this check does not cover. It only reads the contract's mechanics as they exist on-chain today. It says nothing about who is behind the project, whether the team has a history of similar tokens, how the tokenomics are structured over time, whether there are off-chain agreements or legal claims attached to the token, or what the team's intentions are going forward. A clean mechanical reading does not speak to any of that, and an automated check like this one cannot assess intent.
Before deciding anything, it would be worth looking at who holds the unlocked liquidity and whether there's any public commitment, time-locked or otherwise, to keep it in place. It's also worth examining the top 10 wallets individually, since concentration numbers alone don't show whether those are team wallets, exchange wallets, or early investors with no restrictions on selling. Checking the project's social channels, any audit reports from named third parties, and the history of the deploying wallet on the block explorer can also add useful context that this contract-level check cannot provide.
Contracts change after they are checked. Tell us where to reach you and we will say when this one does. Free for three contracts, no account.
We checked 18 points out of 100.
A deep check also reviews the project's public materials, team, tokenomics and disclosures.