Disclaimer
Effective: 22 August 2026
DSH Studios ("we," "us," or "our") operates the website https://dshstudios.com (the "Service"), a community directory that catalogs third-party plugins, agents, skills, and workflows for the open-source DeepSeek Harness (DSH) framework. This page explains the boundaries of what the directory provides and what responsibilities remain yours as a user.
DSH Studios is an independent community project. It is not affiliated with, endorsed by, or sponsored by DeepSeek. References to "DSH" and "DeepSeek Harness" identify the open-source framework for descriptive purposes only and do not imply any partnership, sponsorship, or endorsement.
1. Purpose of this Disclaimer
This Disclaimer is published together with the Terms of Service and the Privacy Policy. It summarizes the boundary between what DSH Studios provides (a discovery surface for third-party plugins) and what remains the responsibility of the operator of the upstream repository and of the user who installs a plugin. By using the Service you confirm that you have read and understood this Disclaimer.
2. No endorsement
Listing does not equal an endorsement or security review. Third-party plugins can access files, credentials, and network resources. Review the source repository before installing.
DSH Studios is an independent community project and is not an official DeepSeek product.
We do not endorse, audit, certify, or warrant any plugin listed on the Service. The presence of a status tag such as Listed, Source verified, Maintained, or Needs review is descriptive of the data we have observed about the repository (public availability, declared fields, recent activity). It is not a security review, a quality rating, or an endorsement. In particular:
Listedmeans the entry is indexed in the directory.Source verifiedmeans the upstream repository URL is publicly accessible at the last sync time and the basic metadata fields match.Maintainedmeans the upstream repository had at least one commit, release, or issue activity within the trailing 12 months at the last sync time.Needs reviewmeans our last sync found the entry stale, the upstream repository inaccessible, or some required metadata field out of date.
A plugin can carry Source verified and Maintained and still be inappropriate for your environment.
3. User responsibility
You are responsible for evaluating whether a plugin is appropriate for your use case and for any consequences of installing or running third-party code. Where install commands are shown, they are reference only. DSH Studios does not execute third-party plugins and does not guarantee compatibility with the current DSH version.
In particular, you are responsible for:
- Reading the upstream repository's
README, license, and changelog before installing. - Inspecting the plugin's declared permissions (file system, network, shell, environment variables).
- Confirming that the plugin's install command produces the expected behavior in a test environment before deploying it to your real workload.
- Maintaining your own backup and recovery plan; DSH Studios makes no commitment to retain historical versions, README exports, or screenshots of any plugin once its listing has been removed.
- Checking the third-party dependencies a plugin brings in (its own transitive dependency tree), and any credentials or tokens those dependencies may require.
4. Third-party risks
Plugins listed here can request access to files, credentials, and network resources. Plugins may, with or without notice, change their behavior between releases, introduce new dependencies, or be republished under a different name by a different actor. Review each plugin's source repository, license, and recent maintenance activity before installing.
We do not control, and we are not responsible for:
- The behavior of any third-party plugin after it is installed in your environment.
- The accuracy of README content or screenshots fetched from upstream repositories.
- The security or privacy practices of GitHub, npm, PyPI, or any other registry through which a third-party plugin is distributed.
- The availability of upstream repositories, READMEs, or assets; if an upstream resource is removed, we may keep the listing for an audit window (up to 90 days) and then remove it.
To report a problematic listing or a suspected compromised plugin, use the channels listed in Section 5 of this Disclaimer.
5. Contact information
To report a problematic listing, request data deletion, ask compliance questions, submit a DMCA notice, or contact the operator for any other reason listed in this Disclaimer, the Privacy Policy, or the Terms of Service, use one of the channels below. We aim to respond to substantive compliance requests within 30 days (15 days for users in the EU/UK, where applicable).
- Email: legal@dshstudios.com for general and legal inquiries, or privacy@dshstudios.com for privacy and data-protection requests. Cloudflare Email Routing forwards these to the operator.
- GitHub: open an issue on the project's public repository for general feedback that does not contain personally identifiable information.
- Postal address (for formal legal notice): the operator's physical address will be added to this section before public launch and should be updated in
reports/legal/disclaimer.mdat the same time as the rendered page.
6. Forward-looking statements and AI-generated listings
Any listing, description, summary, or screenshot on the Service is provided for informational and discovery purposes only. Nothing on the Service is financial, legal, medical, or professional advice. The Service does not produce AI-generated screenshots of in-app interfaces that are not present in the upstream repository, and any screenshot shown is sourced from the upstream README or social preview.
We may, in the future, surface AI-generated explanations, summaries, or translations of upstream content. If we do, we will mark such content visibly (for example with "AI-generated summary" or equivalent) and link back to the source so the original is always inspectable.
7. Changes to this Disclaimer
We may update this Disclaimer from time to time. The "Effective" date at the top of this page reflects the latest update. For material changes, we will email registered users at least 14 days before the change takes effect.