npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

dsh-plugins

v0.1.2

Published

Search and install DeepSeek Harness plugins from the DSH plugin registry

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

gundam9876gundam9876

Keywords

deepseekdeepseek-harnessdshplugin

Readme

dsh-plugins

Search the curated DeepSeek Harness plugin registry locally and install only entries with an exact, checked install specification.

Search needs Node.js 20 or newer. Installation additionally requires the official dsh command and the pnpm command it uses to manage profile dependencies to be available on PATH.

Install

npm install --global dsh-plugins

The installed command is dsp.

Usage

dsp search TUI
dsp show huiliyi37/dsh-tianshu-tui
dsp install huiliyi37/dsh-tianshu-tui --dry-run
dsp install huiliyi37/dsh-tianshu-tui --yes

Batch installation preserves the supplied order and invokes the official Harness command once per plugin:

dsp install owner/first owner/second --profile web --dry-run
dsp install --file plugins.txt --profile web --yes

plugins.txt is UTF-8, one exact owner/repo identifier per line. Blank lines and lines beginning with # are ignored.

The packaged registry always works offline. By default the CLI checks the published static registry at most once every 15 minutes, validates it, and caches it atomically. Use --offline to make no network request or --refresh to force an ETag revalidation. Override the HTTPS registry URL with DSH_PLUGINS_REGISTRY_URL and the cache location with DSH_PLUGINS_CACHE_DIR.

Configuration helpers

dsp config path --profile web
dsp config defaults --profile web
dsp config show --profile web

Harness plugins configure themselves through layered cordis.patch.yml files. This CLI does not invent plugin-specific configuration keys or modify allowBuilds.

config defaults prints the bundle layers. config show also includes the profile and home user layers. Both keep !!js expressions unevaluated; they are composed configuration documents, not evaluated runtime objects.

The displayed npm integrity value was recorded when the Registry entry was checked; the official dsh plugin command still resolves the pinned packageName@version through the user's configured npm registry. It is not an independent artifact-integrity enforcement step.

Third-party plugins execute with the user's privileges and may run package lifecycle scripts. Review the repository and the installation plan before passing --yes.

Before changing a profile, the CLI checks the recorded Node engine and verifies that dsh --version and pnpm --version succeed. --dry-run does not require either command.