Risk Scoring
Sentinel keeps safety or authority evidence separate from Adoption. Standard EVM reports use Contract Safety; Solana reports Authority & Distribution. Where available, Sentinel also derives an overall score from 0 to 100, where higher is safer within the available evidence.
Overall risk bands
| Risk band | Overall score | Interpretation |
|---|---|---|
| Low | 90–100 | Stronger available evidence profile; review the underlying factors |
| Moderate | 70–89 | Some cautionary factors are present |
| Elevated | 55–69 | Material risk or maturity factors need review |
| High | 35–54 | Substantial concerns appear in the available evidence |
| Critical | 0–34 | Severe indicators appear in the available evidence |
When an overall score is provided, its band is a summary, not a safety guarantee. Contract Safety is weighted more heavily than Adoption, and a dangerous contract constrains the overall result. Always read each factor and unknown before acting on a scan.
How the score is calculated
Sentinel collects structured contract and market evidence, scores the applicable safety or authority axis separately from Adoption, then derives an overall score where the report supports one. Missing provider evidence remains unknown rather than counting as a reassuring signal.
1. Honeypot detection
Reviews provider-reported honeypot, cannot-sell, cooldown, transfer-pause, and tax signals. Direct cannot-sell evidence carries more weight than weaker heuristics. The Basic Scan does not execute forked buy and sell transactions.
2. Holder concentration
Measures top-wallet concentration when provider data is coherent, excluding contract, locked, and burn addresses. Concentration influences the Adoption assessment. The Basic Scan does not classify wallets by deployer linkage.
3. Liquidity depth
Aggregates same-chain DEX pool liquidity, leading pool, pool age, and available reserve data. Liquidity uses absolute bands in the Adoption assessment; market-cap rank and trading volume are separate signals. The Basic Scan does not calculate a liquidity-to-market-cap ratio.
4. Owner permissions
Reports owner, mint, pause, blacklist, fee-modification, and proxy-related evidence where providers, ABI data, or verified source expose it. Missing fields remain unknown. This is not an exhaustive permissions or role map.
5. Proxy pattern
Flags reported proxy and upgrade patterns found through provider, ABI, or verified-source evidence. Common proxy patterns can introduce upgrade risk, but a clean result does not prove that no upgrade path exists.
6. Source availability
Checks whether the relevant chain explorer provides verified source and a usable ABI, with compiler and source metadata when available. The Basic Scan does not independently rebuild the source and compare it with deployed bytecode.
What the score does not measure
Sentinel's automated scan is a point-in-time assessment of available evidence. It does not provide:
- Forked trade execution or guaranteed sellability
- Exhaustive contract permissions or role discovery
- Independent source-to-bytecode equivalence testing
- Team identity or track record
- Tokenomics design or vesting schedules
- Off-chain governance or multisig signer reputation
- Legal or regulatory risk
- Market manipulation or wash trading
For a comprehensive assessment, use the Full AI Audit, which covers vulnerability analysis and includes remediation guidance.
Score stability
Scores can change over time as on-chain state changes — liquidity can be removed, ownership can be transferred, new pools can be created. Sentinel's Monitoring tier (coming soon) runs daily re-scans and alerts you when a token's score changes materially.