Overview
Why Molthood exists
Most on-chain tooling answers confidently whether or not it checked anything. That gap is the product.
There is no shortage of tools that will tell you a token is safe. The problem is that almost none of them distinguish between checked and clean and not checked at all, and those two produce identical-looking green ticks.
That is not a small omission. It inverts the meaning of the result. A scanner that could not reach the contract source, could not read the liquidity, and could not resolve ownership will happily show you a page with no warnings on it — and no warnings reads as good news.
The rule
Everything else follows from it. A risk score computed while a check was unavailable is reported as a ceiling rather than a number. A comparison with nothing to compare against returns nothing rather than "no changes". A page with no live source says so instead of showing a plausible placeholder.
The subtle version
The hard case is not a source that fails — it is a source that succeeds and returns nothing. An explorer answering 200 OK with an empty verification field is not saying "unknown"; it is saying the contract is unverified, which is a finding.
Reading that emptiness as "no data" produced no finding at all, and an unverified token scored identically to a verified one. When a source answers successfully with an empty field, something has to decide what the emptiness means.