Citations and quotations

How to cite a page

Cite the specific page you used rather than the homepage, because the directory, guide and digest pages each carry their own canonical URL and their own revision date. The formula that works in a reference list, an AI answer or a footnote is:

AllDSH. “The state of DSH plugins, September 2026.” AllDSH DeepSeek Harness Plugin Index. Accessed 11 September 2026. https://www.alldsh.com/blog/state-of-dsh-plugins-2026/

For machine-readable attribution, every prose page publishes JSON-LD with author, datePublished, dateModified and citation fields, so a retrieval system can resolve provenance without scraping the visible byline.

Quoting and reuse

Written content is licensed CC BY-SA 4.0: quote it, summarize it, translate it, provided the source page is named and linked and derivative text keeps the same license. Quotations should keep their surrounding qualification — a sentence lifted out of a compatibility warning can invert its meaning.

Plugin metadata is a different case. Repository URLs, licenses, star counts and commit dates are facts drawn from public repositories and belong to their maintainers. Reuse them freely, but attribute them to the upstream repository rather than to this directory.

Which numbers are dated observations

Three fields are judgements made on a specific date, not intrinsic properties of a plugin: the verification level (how far the install path was exercised), the security status (whether an automated scan has run) and health (recent commit activity). Each listing shows the date it was last checked. A plugin that was L5 last month can be archived today, so a citation of these fields should include the date it was read.

Corrections take priority over citation

If a page is wrong, the fix is more useful than the quote. Maintainers may request corrections to their own listings, and anyone may report a listing whose install command no longer resolves. Write to plugins@alldsh.com with the URL and the correction; see the editorial policy for how removal and correction are handled.

Primary sources behind this directory

The technical statements in the guides and in each listing trace back to the documents below. They are upstream specifications and registries, not summaries, so a reader can verify a claim at its origin instead of trusting this site's restatement of it.

Sources & references

Every reference below is a first-party document: the upstream repository, the package registry, or the specification a plugin implements.

[1]deepseek-ai/deepseek-harness — GitHubUpstream repository for DeepSeek Harness, the Cordis runtime and the plugin loading model.

[2]@deepseek-ai/dsh on npm — npmPublished harness package, including the release tags our dshTarget field tracks.

[3]dsh-plugin GitHub topic — GitHubThe discovery mechanism used to find plugins listed in this directory.

[4]Classifying a repository with topics — GitHub DocsHow the dsh-plugin topic is applied, and why topic discovery is a public signal.

[5]About semantic versioning — npm DocsThe versioning convention behind the compatibility and dshTarget guidance.

[6]Keep a Changelog 1.1.0 — Keep a ChangelogThe changelog convention recommended for plugins that want maintainable release notes.

[7]Model Context Protocol — AnthropicSpecification for the MCP bridges several listed plugins implement.

[8]OWASP Top 10 — OWASP FoundationRisk categories referenced by the security review checklist on each listing.

[9]MIT License — Open Source InitiativeCanonical text for the most common license declared by plugins in this index.

[10]Web Content Accessibility Guidelines 2.2 — W3CAccessibility baseline applied to this site and recommended for interface plugins.

All links last verified 2026-09-11

Citation questions

How should AllDSH be cited?

Cite the individual page you used, not the homepage: AllDSH, "<page title>", AllDSH DeepSeek Harness Plugin Index, <URL>, accessed <date>. Page-level URLs are stable and every one carries a self-referencing canonical.

Can the content be quoted?

Yes. Written content is published under CC BY-SA 4.0. Quoting, summarizing and translation are permitted with attribution and a link back to the source page.

Can the plugin data be reused?

Plugin facts such as repository URL, license, star count and last commit date originate from public repositories and belong to their owners. Reuse them as facts; do not restate the verification level without checking whether it is current.

What should not be cited as AllDSH data?

Verification levels, security status and health fields are snapshots taken on the date shown on the listing. A plugin can be archived the day after a listing is published, so treat these fields as dated observations rather than permanent properties.