Facts keep their provenance.
Every published fact is designed to retain its source and observation time, plus a fixed commit when repository evidence is involved.
See how evidence is collectedCurrent evidence inputs
Current evidence draws on these source materials and recorded metadata.
- Upstream reference
- The DeepSeek Harness official repository
- Repositories
- GitHub repositories and immutable commits
- Fixed snapshot
- A fixed GitHub Commit Object and complete Tree
- Approved files
- The approved Manifest and Patch Blob objects
- Root README
- At most one supported root README up to 64 KiB, reduced to heading-presence facts and file identity
- Selected paths
- Tree-only license and shell path observations
Static-analysis limits
Published static-analysis records do not query npm Registry or retain README text, entry source, license text, or shell source.
Unsupported syntax is a scope limit, not a claim that a plugin cannot run.
Privacy and hosting
On this site
DSH Hunt uses Google Analytics to measure page visits. By default, Google Analytics receives the full page URL, which may include query parameters such as site search terms. The site does not provide user accounts or session replay, and it does not ask visitors for personal details through an on-site form.
See Google's privacy policy for how Google handles data.
At the host
The site is hosted on Cloudflare, which receives connection and request metadata needed to deliver and protect the pages. Cloudflare Worker invocation logs can include the request method and URL, including a query string unless it is redacted.
See Cloudflare's privacy policy for the host's terms and practices.
Published observations
DSH Hunt retains published source observations so that later source deletion or unavailability can be shown as inaccessible rather than silently erased. A correction or withdrawal does not rewrite the fixed source facts.
Corrections and public feedback
Maintainers and community members can submit corrections with primary evidence through the public GitHub community repository. Feedback and corrections submitted there may be publicly visible and are governed by GitHub and community repository policies.
Open a correction issueKeep private contact details, credentials, or sensitive information out of URL query strings and public issues.
