An independent evidence project.

DSH Hunt is an independent community project. It is not affiliated with DeepSeek, does not represent DeepSeek's official views, and is not endorsed by DeepSeek.

Read how the evidence is collected

Ownership and limitations

Third-party ownership

Third-party plugins, source code, names, and brand assets belong to their respective authors and rights holders.

Evidence has limits

DSH Hunt analysis may contain errors or become outdated as upstream projects change. Static analysis is not a security audit, and it does not establish runtime compatibility.

Data sources

Plugin suggestions may come from public sources and community submissions. Maintainers verify and normalize source details before a candidate enters the application import process.

Source-linked structural and static reports use fixed public source revisions. Repository and Registry metadata carry observation times. Submitted plugins are not executed.

A community submission is a review request and does not guarantee a listing or publication.

Published catalog dataset

The plugin catalog, registry observations, and version-change records are served from one validated data bundle. The structural-evidence dataset has a separate Day 07 release ID.

Catalog views snapshot ID
275262d658f470e3dd4309660db5e581d737fcef33f0b8400fc3583fa2ca6a02
Structural-evidence release ID
0e065067a295f5fc27b7594ebc067d28edd2ed526693c5d2e6e3bf8c5ec5127a

The application build hash identifies the combined generated-data inputs.

How contributions move through review

Choose the matching public form below or from the community guide. False-positive appeals and methodology proposals use their own forms.

For a plugin suggestion

Include its public repository, package or bundle path, a fixed source commit when available, license evidence, and a documented install command or “Not found.”

For an evidence correction

Identify the page and exact field, copy the displayed value, propose a value, and link the public primary source at the relevant commit.

A maintainer reviews the source, identity, duplicate status, license evidence, and scope by hand. Submitted text and install commands are reference material; DSH Hunt does not execute them.

  1. New

    A maintainer checks scope and required evidence.

  2. Needs information or under review

    Missing evidence is requested, or the pinned sources and claims are checked.

  3. Accepted or rejected

    The review decision records whether the proposed evidence supports the request.

  4. Published

    Accepted changes move through release checks; this status is used only after a release is live and the affected page is checked.

Acceptance is not publication, a security endorsement, or runtime approval. There is no promised response time.

Community feedback

These routes lead to the public GitHub community repository and Issue forms. Opening a form does not submit a request. Package evidence pages provide correction links with the exact report and field context.

GitHub Issues and pull requests are public. Do not include secrets, private source code, sensitive vulnerability details, or information you are not authorized to share.