Is Searchwave safe and trustworthy?

tashan scores Searchwave on public evidence — tashan score 23.0/100, it is currently abandoned, note: a single primary maintainer (bus-factor risk). Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Searchwave?

Configure it from its source repository — it is a remote / registry server.

Who maintains Searchwave?

1 GitHub contributors, source: rowbradley/searchwave.

‹ The Index

Searchwave

plugin

Searchwave is a research synthesis plugin for Claude Code with two command families, Wave and Deepwave. Think of it as ‘minimum viable context collection’ for both humans and agents. Wave delivers quick ~90-second research with parallel web searches and synthesis — ideal for rapid context collection. Deepwave offers depth-selectable research (Quick/Standard/Max) with Opus synthesis, up to 10 parallel searches, inline citations, and thesis-driven analysis for comprehensive topic coverage in 7...

Works with: Claude Code (native)
native: this artifact type is that client's own format

Install (Claude Code):

/plugin marketplace add anthropics/claude-plugins-community
/plugin install searchwave@claude-community

solid

“9 worked examples; short of deep on per-tool docs”

This grade is wrong ›

Looking for a replacement? npx tashan-cli doctor is free and tells you everything above about your whole config. tashan Pro names the replacement — which one, and how it measures. $6/mo.

tashan score: 23.0
Instruction depth: 66.0 (solid — documents the job properly, with examples you could follow)
Adoption: 1 repos
Upkeep: 39.0
Freshness: 46.0
Evidence coverage: 84% of the inputs this score can use — the rest are unknown, and the score is discounted for it
Health: abandoned
GitHub stars: 5
Contributors: 1
License: MIT

Security audit

Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.

What changed recently

2026-08-16 searchwave now reads as abandoned, was active Upkeep signals stopped, under enough issue pressure that it is not merely finished.

You are reading this because you came looking. tashan Pro gives tashan doctor the history behind it, so a run over your own config says which of YOURS moved.

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

We recorded 1 change to Searchwave in the last 45 days. Pro tells you on the day — for the servers in your own config, not the ones you thought to look up.

The whole series behind any row, back to the first day we measured it
The replacement, named — not just the news that something died
tashan doctor over your own config, on your own machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/plugin-rowbradley-searchwave-searchwave.svg)](https://tashan.sh/capability/plugin-rowbradley-searchwave-searchwave.html)

source ↗ · plugin:rowbradley/searchwave/searchwave

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-09-13 · scorer s5 · how · something wrong here?