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-proxy-manager

v0.1.3

Published

Manage proxy settings in DeepSeek Harness. A single settings page sets, inspects and clears the proxy configuration of the developer tools.

Readme

English | 中文

dsh-proxy-manager

Set, inspect and clear the proxy configuration of the developer tools on this machine from one page in Settings → Proxy: 13 tools are built in, your own can be added, and one click enables or clears the proxy for all of them.

The Proxy page in Settings: the proxy address and bypass list at the top, then the searchable list of tools with their state, address and configuration file

What it does

  • One list, every tool. Each row shows whether the proxy is on, the address it uses, and the exact configuration file that holds it.
  • One click to enable or clear. Enable for all / Clear for all, or the switch on a single row. Files are edited in place: comments, ordering and unrelated keys survive.
  • Use the system proxy. Reads the proxy the operating system itself is set to and fills it in, including the bypass list.
  • Open the configuration file. Opens it in the default text editor; rows whose file does not exist yet are marked and cannot be opened.
  • Pin, search, page. Pinned tools stay on top, configured tools sort above unconfigured ones, missing files go last; search filters by name, id, path, category or address; 10 rows per page.
  • Extensible three ways. Add software from the page, add a built-in adapter in code, or register one from another plugin at runtime.
  • Available to the agent too. The proxy_manager tool reads the same state and performs the same actions as the page.

Install

  1. In Plugins, choose Add plugin, enter dsh-proxy-manager, and press Install — or run dsh plugin --profile <profile> add dsh-proxy-manager, where <profile> is the one you boot (for example web).
  2. Choose Enable now, or switch on the Proxy manager row.
  3. Restart DeepSeek Harness once — the Host module and the browser bundle are loaded with a new process. After that, toggling the row is enough to reload the plugin.
  4. Open Settings → Proxy.

To upgrade, reinstall: uninstall the row and add dsh-proxy-manager again (dsh plugin --profile <profile> add dsh-proxy-manager@latest).

Supported tools

| Tool | Configuration file | Written keys | | --- | --- | --- | | Git | ~/.gitconfig | [http] proxy, [https] proxy | | npm | ~/.npmrc | proxy, https-proxy | | pnpm | ~/.npmrc (shared with npm) | proxy, https-proxy | | Yarn | ~/.yarnrc.yml | httpProxy, httpsProxy | | Cargo | ~/.cargo/config.toml | [http] proxy | | pip | ~/Library/Application Support/pip/pip.conf (macOS), ~/.config/pip/pip.conf (Linux), %APPDATA%\pip\pip.ini (Windows) | [global] proxy | | Maven | ~/.m2/settings.xml | one <proxy> element (dsh-proxy-manager) | | Gradle | ~/.gradle/gradle.properties | systemProp.http(s).proxyHost/proxyPort/nonProxyHosts | | DeepSeek Harness | $DSH_HOME/.env | HTTP_PROXY, HTTPS_PROXY, NO_PROXY | | Docker | ~/.docker/config.json | proxies.default.httpProxy/httpsProxy/noProxy | | Shell environment | ~/.zshrc / ~/.bashrc (Windows: PowerShell profile) | HTTP_PROXY, HTTPS_PROXY, NO_PROXY | | curl | ~/.curlrc | proxy, noproxy | | wget | ~/.wgetrc | http_proxy, https_proxy, no_proxy |

The shell entry covers every tool that only reads environment variables — Go, kubectl, Helm, Terraform, aws, uv, Poetry, Bundler, Homebrew.

Use it

  1. Open Settings → Proxy.
  2. Enter the proxy address (for example http://127.0.0.1:7890), or press Use system proxy to take the system value, and the bypass hosts.
  3. Press Save, then Enable for all — or flip the switch on the tools you want.
  4. Use Clear for all, or a single switch, to remove the proxy again.

Programs that are already running keep the proxy they read at start-up: restart the tool, or open a new terminal. DeepSeek Harness itself applies the change on its next start.

Add software

From the page. Open Add software at the bottom of the list and describe the tool: display name, file format, configuration file, section, key, and what that key holds (the whole URL, host, port or bypass list). The adapter is stored in this plugin's own state file.

In code. Add src/host/adapters/<tool>.ts:

import type { ToolSpec } from '../core/types.ts'

export const bun: ToolSpec = {
  id: 'bun',
  name: 'Bun',
  category: 'javascript',
  kind: 'toml',
  path: '~/.bunfig.toml',
  section: 'install',
  fields: [{ key: 'proxy', part: 'url' }],
}

then list it in builtinAdapters in src/host/adapters/index.ts. The page, the HTTP endpoint and the agent tool all read that one table.

From another plugin:

const dispose = ctx.proxyManager.registerTool({ id: 'my-tool', name: 'My tool', kind: 'json', path: '~/.my-tool/config.json', fields: [{ key: 'proxy.url', part: 'url' }] })

Adapter fields

| Field | Meaning | | --- | --- | | kind | File dialect: ini ([section] + key = value), props (key=value), yaml (top-level key: value), toml ([table] + key = "value"), json (dotted path), env (KEY=VALUE), shell (managed export block), xml (managed <proxy> element) | | path | One path, a list of candidates (the first existing one wins), or a per-platform table; ~, $DSH_HOME and %APPDATA% expand | | section | Section or table name for ini / toml; a field may override it | | fields[].key | Key, dotted JSON path, or element name inside the managed block | | fields[].part | url (whole address), scheme / host / port (stored separately), noProxy | | fields[].transform | jvmNoProxy converts the bypass list to the JVM's | form | | binary | Executable checked against PATH for the "not installed" hint |

Agent tool

proxy_manager with action:

  • status — every tool, its proxy and its configuration file
  • enable — write the proxy (tools limits it to specific ids, proxy overrides the saved address for the call)
  • disable — remove it (optionally for tools)
  • system — what the operating system proxy is

Notes

  • Use system proxy reads the manual proxy of the OS (macOS scutil --proxy, Windows Internet Settings, GNOME gsettings). An automatic configuration script (PAC) or a TUN/VPN adapter exposes no fixed address, and the page says so instead of guessing.
  • pnpm and npm share ~/.npmrc, so enabling one shows both as enabled — that is the real state.
  • Windows and Linux paths, registry/GNOME detection and explorer/xdg-open are implemented and unit-tested, but only macOS has been run end to end.

Development

pnpm 12 is pinned in package.json (packageManager); pnpm-workspace.yaml allows the one build script development needs (esbuild).

pnpm install
pnpm typecheck
pnpm build     # lib/loader.js, lib/host.js, lib/client.js
pnpm test

pnpm build writes the committed lib/ artifacts; reload the plugin row (or restart once after installing) to load them.

License

MIT — see LICENSE.