Skip to content

How Docdrift Verified works

Docdrift Verified means Docdrift checked these facts in the code and on the site. It doesn't guarantee that the product works, is secure or makes money.

Method version 1 · Sep 30, 2026

Features verified

How we verify it
Features listed on the checked pages of the verified site that Docdrift matched to a route, screen or handler it found in the code itself, counted once per matched capability. Features Docdrift can't match aren't shown, and are never called false.
How it could be gamed
Listing features that exist in the code only as placeholders, describing the same feature several times in different words, or showing Docdrift a different page, including by recognizing the server Docdrift reads from.
What catches it
Handlers that do nothing, only return a fixed response or only call a function that returns one don't count. Each capability counts once, however many times the site describes it. Matching uses Docdrift's own names and the code, never names the founder edits. Docdrift reads each page with a browser's user agent, without running scripts, and flags pages that differ from what it gets as Docdrift. It doesn't detect a site that recognizes Docdrift's server; anyone can report the profile.

Verified since

How we verify it
The day Docdrift started watching this project.
How it could be gamed
It can't be set or backdated by the founder.
What catches it
—

Code size

How we verify it
Lines of the team's own code, tests included, without the vendored, generated or duplicated files that Docdrift recognizes or that .gitattributes marks. Capabilities are counted with Docdrift's own grouping, only in the languages it analyzes.
How it could be gamed
Padding with generated code or trivial tests, or splitting capabilities.
What catches it
Capabilities are shown next to it and splitting doesn't change their count. Unusual growth is flagged, even if the founder hides this metric.

Uptime (90 days)

How we verify it
Docdrift requests a URL the founder chose every 5 minutes from its own server and confirms failures before counting them.
How it could be gamed
Pointing it to a page that is always up.
What catches it
Nothing can prove the URL is the product people use, so it's marked "Declared".