Evidence tiers
| Tier | Meaning |
|---|---|
| Official | Directly supported by DeepSeek’s product site, repository, or documentation. |
| Install verified | Package operation reproduced in named versions and environment. |
| Feature verified | A named task completed after installation. |
| Repository evidence | Identity or behavior described by source, not reproduced by HarnessBase. |
| Community observed | A report or demonstration exists but remains unverified. |
| Unknown | Evidence is absent or insufficient. |
How sources appear on the website
- Official or repository facts: a direct source link and checked date appear beside the claim or in the page’s provenance ledger.
- YouTube observations: the cited video is embedded with title, channel, publication date, reviewed date, useful segment, and a visible “not verification” boundary.
- Reddit reports: HarnessBase uses Reddit’s official embed when a post materially informed a test. The embed can reflect edits or deletion; the report remains community evidence.
- Direct tests: the page shows a stable HarnessBase record ID, date, exact versions, OS/runtime environment, measured result, and what was not tested.
Minimum retained test record
Source URL or package artifact, observation date, DSH/plugin/runtime versions, OS environment, test steps, expected and actual result, install/load/feature status, permission observations, failures, cleanup, and freshness state.
Raw logs and machine-local artifacts are retained for review, but local paths, cookies, credentials, secrets, and unrelated user data are not published. The public record ID connects the visible summary to the retained test without exposing the workstation.
Tests are split at real boundaries
A package can install while its client UI fails. A plugin can load while its external message delivery remains Unknown. An MCP Tool can work locally without proving TLS, proxy, or production authentication. HarnessBase publishes these as separate results instead of collapsing them into one green check.
Corrections and freshness
Until a public correction channel is configured, use the repository associated with this site. A correction changes a current record only after the source or test is rechecked. Release changes, package changes, edited community sources, and expired observation dates trigger a new review.