Submit a Plugin

Getting your plugin into the registry validates dsh.so's whole purpose: the moment a developer actively submits their plugin, dsh.so becomes an ecosystem hub rather than a content site. Paste your repository URL below — the checker pulls it, validates the format, runs a security scan, and prepares a schema-valid registry entry for you.

Acceptance criteria

Scan coverage: vet runs AST analysis on JS/TS (plus shell/PowerShell download-and-exec patterns); other languages are covered by the dsh heuristic scanner.

Check your repository

Supports public repos on GitHub, Gitee and GitLab. Examples: github.com/owner/repo · gitee.com/owner/repo · owner/repo (GitHub)

Entry type

Desktop shells and other standalone applications that bundle the dsh runtime are listed as ecosystem apps (shown as L5 · ecosystem app): they get a GitHub repository link instead of an install command and are exempt from the install-verification ladder (the security scan still applies).

Security scan powered by
dsh.so
dsh-plugin-vet

What happens next

Report a compatibility check

You ran a plugin on a specific dsh version and it worked (or didn't)? That is exactly the data the ecosystem needs — and dsh.so is honest about it: no plugin is Verified yet, and the only way to change that is real reports. Copy the template below, paste it into the official Discussions, and dsh.so will fold the result into the version compatibility matrix.

Template · copy & post

Questions?

Ask in the official DSH Discussions or open a regular issue in the dsh.so repository.

Was this page helpful?