Skip to content
Back to search

dsh-web-search-searxng

A SearXNG-backed WebSearchProvider for the DeepSeek Harness web capability seam (ctx.web).

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/chinng-inta--dsh-web-search-searxng/badge.svg)](/listings/chinng-inta--dsh-web-search-searxng)

HTML

<a href="/listings/chinng-inta--dsh-web-search-searxng"><img src="/api/listings/chinng-inta--dsh-web-search-searxng/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

From npm

dsh plugin --profile web add dsh-web-search-searxng

From this repository

dsh plugin --profile web add github:chinng-inta/dsh-web-search-searxng

A git dependency ships no `lib/`, so the package builds itself through its `prepare` script — and pnpm blocks install scripts until you allow them. The first run therefore fails and prints the exact key to allow. Add it to your profile's `pnpm-workspace.yaml` and re-run:

allowBuilds:
  "dsh-web-search-searxng@https://codeload.github.com/chinng-inta/dsh-web-search-searxng/tar.gz/<commit-sha>": true

The key pins a commit, so it changes whenever you install a newer revision. Building from source also needs the dev toolchain fetched (~20 s versus ~2 s for the registry). Prefer npm unless you are tracking unreleased changes.

Either way

The package declares `dsh.bundle`, so a single command also activates it: the bundle patch inserts the provider row and selects it on the `web` row. Point it at your instance and restart:

export SEARXNG_URL=http://searxng.internal:8888

Verify the composition before booting:

dsh --profile web --dump-config | grep -A3 'id: web'

Your instance must serve JSON

SearXNG does not enable the JSON API by default. In the instance's `settings.yml`:

search:
  formats:
    - html
    - json

Without it the endpoint answers with the HTML result page, and this provider fails with a message naming the fix rather than a parse error.

A public instance is a poor backend: most refuse programmatic access (HTTP 403 from a bot filter) or rate-limit aggressively. Run your own.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 242 lines
  1. # dsh-web-search-searxng
  2. A [SearXNG](https://docs.searxng.org/)-backed `WebSearchProvider` for the
  3. [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) web capability seam (`ctx.web`).
  4. SearXNG is a self-hosted metasearch engine. One search here is a plain retrieval call against the
  5. instance's `/search?format=json` endpoint, so unlike the shipped DeepSeek provider it needs **no API
  6. key** and costs **no model turn** — the shipped provider issues a full Messages request with the
  7. native `web_search` server tool, paying latency and generated tokens for every search.
  8. This is an **implementation** package: it registers a provider into `ctx.web` and does **not**
  9. register a model-facing tool. `@deepseek-ai/dsh-tool-web` owns `web_search`, its schema, its prompt
  10. guidance, and the result card. Installing this package makes that existing tool work against your
  11. own instance.
  12. ## Install
  13. ### From npm
  14. ```bash
  15. dsh plugin --profile web add dsh-web-search-searxng
  16. ```
  17. ### From this repository
  18. ```bash
  19. dsh plugin --profile web add github:chinng-inta/dsh-web-search-searxng
  20. ```
  21. A git dependency ships no `lib/`, so the package builds itself through its `prepare` script — and
  22. pnpm blocks install scripts until you allow them. The first run therefore fails and prints the exact
  23. key to allow. Add it to your profile's `pnpm-workspace.yaml` and re-run:
  24. ```yaml
  25. allowBuilds:
  26. "dsh-web-search-searxng@https://codeload.github.com/chinng-inta/dsh-web-search-searxng/tar.gz/<commit-sha>": true
  27. ```
  28. The key pins a commit, so it changes whenever you install a newer revision. Building from source also
  29. needs the dev toolchain fetched (~20 s versus ~2 s for the registry). Prefer npm unless you are
  30. tracking unreleased changes.
  31. ### Either way
  32. The package declares `dsh.bundle`, so a single command also activates it: the bundle patch
  33. inserts the provider row and selects it on the `web` row. Point it at your instance and restart:
  34. ```bash
  35. export SEARXNG_URL=http://searxng.internal:8888
  36. ```
  37. Verify the composition before booting:
  38. ```bash
  39. dsh --profile web --dump-config | grep -A3 'id: web'
  40. ```
  41. ### Your instance must serve JSON
  42. SearXNG does not enable the JSON API by default. In the instance's `settings.yml`:
  43. ```yaml
  44. search:
  45. formats:
  46. - html
  47. - json
  48. ```
  49. Without it the endpoint answers with the HTML result page, and this provider fails with a message
  50. naming the fix rather than a parse error.
  51. A public instance is a poor backend: most refuse programmatic access (HTTP 403 from a bot filter)
  52. or rate-limit aggressively. Run your own.
  53. ## Configuration
  54. The configuration is this plugin row's `config`. `baseURL` additionally falls back to `$SEARXNG_URL`
  55. when the row does not set it, so nothing else is needed to get started: export the variable and the
  56. provider is configured.
  57. Every key is declared `volatile`, which since dsh 0.1.7-rc.2 means two things: the harness settings
  58. service may edit it, and an edit updates the running plugin **in place** (no restart). The provider
  59. reads the row per search, so an edit reaches the next search, and clearing `baseURL` falls back to the
  60. environment again rather than stranding the provider on a value it can no longer see. Registration
  61. itself never moves, so provider selection does not flicker when configuration changes.
  62. There are two ways to set it:
  63. - **The Plugins page.** Open this package, then the configure control on its `web-search-searxng`
  64. row. The page edits the instance URL and the search language, and saves into the active profile's
  65. patch (`$DSH_HOME/profiles/<profile>/cordis.patch.yml`).
  66. - **A patch row**, in your profile patch or a `--patch` overlay:
  67. ```yaml
  68. - id: web-search-searxng
  69. config:
  70. baseURL: http://searxng.internal:8888
  71. language: ja
  72. categories:
  73. - general
  74. - news
  75. ```
  76. A patch row replaces the targeted row's **whole** `config`, so restate every key you want. And a row
  77. you set in a `--patch` overlay sits above the profile patch the Plugins page writes to: a save there
  78. still changes the running value, but it is not persisted, and the overlay wins again at the next boot.
  79. All keys are optional.
  80. | Key | Default | Meaning |
  81. |---|---|---|
  82. | `baseURL` | `$SEARXNG_URL` | Instance root; `/search` is appended. Missing or non-http(s) makes the provider report unavailable rather than fail every search. |
  83. | `categories` | instance default | `categories=` filter, e.g. `['news']`. |
  84. | `engines` | instance default | `engines=` filter, e.g. `['duckduckgo', 'brave']`. |
  85. | `language` | instance default | `language=` filter, e.g. `ja`, `en-US`. |
  86. | `timeRange` | unset | `time_range=` filter: `day` / `week` / `month` / `year`. |
  87. | `safesearch` | instance default | `safesearch=`: `0` off, `1` moderate, `2` strict. |
  88. | `timeoutMs` | `10000` | Resource backstop for one search. |
  89. | `maxSnippetChars` | `500` | Per-source snippet cap. |
  90. | `headers` | none | Extra request headers, e.g. for an instance behind an authenticating proxy. |
  91. Upgrading from `0.4.x`: the `web-search-searxng:` section of `$DSH_HOME/settings.yaml` is no longer
  92. read — dsh 0.1.7 removed that document. dsh imports it once into the profile patch of the first
  93. profile that boots (and renames the file to `settings.yaml.imported`); check the result landed where
  94. you expect.
  95. Every search-shaping knob is a **deployment setting, not a model argument**. The seam's
  96. `WebSearchRequest` is deliberately just `query` + `maxResults`; provider-neutral controls (recency,
  97. domain filters, search depth) are named deferred work upstream. Keeping them in config is what makes
  98. this provider substitutable for the shipped ones.
  99. `timeoutMs` is a resource backstop, not the model-facing tool-call budget —
  100. `@deepseek-ai/dsh-tool-call-timeout-policy` owns that via `tool-web`'s `searchTimeoutMs`. Leave this
  101. below the tool budget so a slow instance surfaces as a provider failure rather than a tool timeout.
  102. ## Provider selection
  103. The bundle patch sets `web.searchProvider: searxng`. This is required, not opinionated.
  104. The seam auto-selects only when exactly **one** registered provider is usable, and
  105. `@deepseek-ai/dsh-web-search-deepseek` reports usable whenever a credential *resolver* exists — which
  106. its own `apply()` always supplies — so it answers `available() === true` on a stock composition even
  107. with no key configured. Registering a second provider without naming one would make every search fail
  108. with `WEB_PROVIDER_AMBIGUOUS`.
  109. Bundle layers apply before your profile's `cordis.patch.yml`, the home patch, and any `--patch`
  110. overlay, so you can always override the choice. But note that a patch replaces the targeted row's
  111. **whole** `config`: if you patch the `web` row yourself for anything else, restate
  112. `searchProvider: searxng` there too.
  113. ## Mapping
  114. | SearXNG | Seam |
  115. |---|---|
  116. | `results[].url` | `sources[].url` (required; results without one are dropped) |
  117. | `results[].title` | `sources[].title` |
  118. | `results[].content` | `sources[].snippet`, capped at `maxSnippetChars` |
  119. | `results[].publishedDate` | `sources[].publishedAt` |
  120. | `answers[]` | `content`, newline-joined; omitted when empty |
  121. Sources are deduplicated by URL, because a metasearch merges engines that routinely return the same
  122. page. Blank strings are treated as absent rather than emitted as empty fields — the seam's optional
  123. fields exist so an adapter never has to invent them.
  124. `truncated` is always `false` from this provider: the seam owns `maxResults` enforcement, and
  125. reporting our own truncation would misattribute whose bound cut the list.
  126. ## Errors
  127. Failures are `WebError`s the tool layer turns into a readable tool result.
  128. | Situation | Code |
  129. |---|---|
  130. | Caller cancelled | `WEB_ABORTED` |
  131. | `timeoutMs` elapsed | `WEB_PROVIDER_ERROR` |
  132. | Non-2xx from the instance (403 carries a bot-filter hint) | `WEB_PROVIDER_ERROR` |
  133. | Response was not JSON (usually `formats` misconfiguration) | `WEB_PROVIDER_ERROR` |
  134. | Unparseable body | `WEB_PROVIDER_ERROR` |
  135. `available()` is a cheap synchronous check — a parseable `http(s)` base URL — as the seam requires;
  136. it never touches the network.
  137. Redirects are refused (`redirect: 'error'`). A self-hosted instance has no reason to redirect a
  138. search, and following one would send the query to a host the deployment never configured.
  139. ## Known limitations
  140. - **`maxResults` is not pushed down.** SearXNG exposes no result-count parameter, so the instance
  141. returns its full first page and the seam truncates. This bounds tokens, not the instance's work.
  142. - **`publishedDate` is usually absent.** General web engines rarely date results; news engines
  143. usually do. Filter with `categories: ['news']` if you need dates.
  144. - **Infoboxes are not surfaced.** They are structured entity cards rather than an answer to the
  145. query, so flattening them into `content` would present them as one.
  146. - **No per-engine failure reporting.** SearXNG reports `unresponsive_engines[]` on partial failures;
  147. the seam's result shape has nowhere to put it, so a degraded search looks like a thin one.
  148. ## Compatibility
  149. | This package | DeepSeek Harness |
  150. |---|---|
  151. | `0.5.0`+ | `0.1.7-rc.2` |
  152. | `0.4.0` | `0.1.2-rc.1` – `0.1.5-rc.3` |
  153. | `0.3.3` – `0.3.x` | `0.1.0-rc.8` – `0.1.1-rc.2` |
  154. | `0.1.x` – `0.3.2` | `0.1.0-rc.6` |
  155. **Every row is mutually exclusive**: nothing here is backward compatible, and nothing older is
  156. forward compatible. Installing the wrong pair does not merely lose this card — it fails the whole
  157. Web UI's plugin load, because the breakages surface as an unanswerable client `require` or an
  158. invalid slot registration ([#1](https://github.com/chinng-inta/dsh-web-search-searxng/issues/1)):
  159. - rc.8 dropped `@deepseek-ai/dsh-client-web-react` from the loader's seed table. Up to `0.3.2`
  160. this package imported `bindSnapshotSelector` from it. `0.3.3` hands its store to the renderer
  161. through the slot inject face's `hooks` compartment instead, which is where rc.8 synthesizes
  162. selector hooks.
  163. - rc.8 turned `settings.plugin.item` from a `list` slot (`id` + `order`) into a `keyed` one
  164. (`key` = the settings namespace the card edits). `0.3.3` registers the keyed way, which rc.6
  165. rejects.
  166. - 0.1.2-alpha.1 deleted `@deepseek-ai/dsh-client-runtime` outright. Up to `0.3.x` this package
  167. took `createSnapshotStore` from it and named it in `dsh.client.inject`; `0.4.0` takes the same
  168. function from `@deepseek-ai/dsh-client-store` (a seed the frontend now hands the loader) and
  169. drops the phantom from `inject`, which would otherwise leave the row pending forever.
  170. - 0.1.2-alpha.2 deleted the `settingsNamespace()` and `installSettingsSection()` helpers from
  171. `@deepseek-ai/dsh-settings`. `0.4.0` uses a bare namespace literal and calls
  172. `settings.installSection` inside `ctx.inject(['settings'], …)`, which is now the attach/detach
  173. lifecycle.
  174. - 0.1.7-rc.2 removed the shared `settings.yaml` together with `settings.installSection`: settings
  175. became each plugin row's own `config`, editable where the schema marks a field `volatile` and
  176. delivered to `apply` as live references. `0.5.0` marks every key volatile and reads them per search;
  177. `0.4.0`'s host half calls the removed method, so its settings never attach. The same release deleted the settings page's
  178. `settings.plugin.item` slot; `0.5.0` registers on the Plugins page's `plugins.row.config`
  179. (keyed `dsh-web-search-searxng#web-search-searxng`) instead.
  180. `0.3.0` shipped the settings card without its stylesheet — it works, but renders with browser
  181. defaults. Use `0.3.1` or later.
  182. The harness is a developer preview with breaking changes between release candidates, and its
  183. packages publish the active line under the **`next`** dist-tag (`latest` still points at the older
  184. `0.0.1-rc.1`). Pin your harness version.
  185. ## License
  186. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.