Is Dev Harness CLI safe and trustworthy?

tashan scores Dev Harness CLI on public evidence — tashan score 37.0/100, it is currently active, note: a single primary maintainer (bus-factor risk), no known advisories against the current release, it runs a script at install time. 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 Dev Harness CLI?

In Claude Code: run `claude mcp add dev-harness-cli -- npx -y dev-harness-cli`. In Cursor / Claude Desktop, add it to mcp.json / claude_desktop_config.json.

Who maintains Dev Harness CLI?

source: bakr-bagaber/dev-harness.

‹ The Index

Dev Harness CLI

npm

Agent-agnostic development harness for AI coding agents — gated phase pipeline with a next-step trajectory engine, built-in MCP server, craft skills library, and deterministic gate validation. Works inside Claude Code, Codex, Cursor, VS Code, and any MCP-

Works with: Claude Code, Cursor, Claude Desktop, Codex CLI, Gemini CLI, Cline, Windsurf, VS Code (installable)
installable: each client documents how to load an MCP server of this type — that is the client's promise, not a claim verified against this capability

Install (Claude Code):

claude mcp add dev-harness-cli -- npx -y dev-harness-cli

tashan score: 37.0
Adoption: 5/wk
Upkeep: 65.0
Freshness: 81.0
Evidence coverage: 100% of the inputs this score can use
Health: active
License: MIT

Security audit

Every finding is shown in full — which advisory, the version that fixes it, and the exact command run at install time. Nothing in this audit is behind a licence.

No known advisoriesclearchecked against OSV for 5.1.0 — this package, not its dependency tree

Runs a script at install timecodenode -e "try{process.stdout.write('dev-harness installed. Run: npx dev-harness --help\n')}catch(e){}"

No access inferred from declared dependenciesnothing it depends on reaches files, shell or network. This reads declarations only — built-in APIs are invisible to it, so absence of a declaration is not absence of access

No build provenanceno attestation — the published artifact cannot be traced to its source

What changed recently

2026-08-11 dev-harness-cli now runs a script when it installs Install-time code executes on your machine before you have used the tool once, and it did not do this before.

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 Dev Harness CLI 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/pkg-dev-harness-cli.svg)](https://tashan.sh/capability/pkg-dev-harness-cli.html)

npm ↗ · source ↗ · pkg:dev-harness-cli

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?