Is Testers safe and trustworthy?

tashan scores Testers on public evidence — tashan score 60.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, its declared dependencies reach: browser, database. 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 Testers?

In Claude Code: run `claude mcp add hasna-testers -- npx -y @hasna/testers`. In Cursor / Claude Desktop, add it to mcp.json / claude_desktop_config.json.

‹ The Index

Testers

npm

AI-powered QA testing CLI — spawns cheap AI agents to test web apps with headless browsers

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

Category: Dev Tools & CI — see all ranked ›

Work: Test automation · Browser automation

Who it is for: Software engineer · Operations

Install (Claude Code):

claude mcp add hasna-testers -- npx -y @hasna/testers

tashan score: 60.0
Adoption: 301/wk
Upkeep: 71.0
Freshness: 92.0
Evidence coverage: 100% of the inputs this score can use
Health: active
License: Apache-2.0

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 0.0.91 — this package, not its dependency tree

Runs a script at install timecodemkdir -p $HOME/.hasna/testers/screenshots $HOME/.hasna/testers/browser/profiles 2>/dev/null || true

Drives a browser · Connects to databasesfrom declared dependencies

Can carry remote content into your agentit can pull third-party text into the model's context — treat what it returns as untrusted input

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

What changed recently

2026-08-11 @hasna/testers now reaches browser, database Its declared dependencies reach further into your machine than they did before.
2026-08-24 @hasna/testers published 0.0.108, was 0.0.91 A new release is available.
2026-08-25 @hasna/testers published 0.0.109, was 0.0.108 A new release is available.

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 4 changes to Testers 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-hasna-testers.svg)](https://tashan.sh/capability/pkg-hasna-testers.html)

npm ↗ · source ↗ · pkg:@hasna/testers

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?