Is Buggazi safe and trustworthy?

tashan scores Buggazi 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. 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 Buggazi?

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

‹ The Index

Buggazi

npm

Project management for coding agents. Bugs, features, sprints. Streamable HTTP + SSE remotes.

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: Project management

Who it is for: Product manager · Operations

Install (Claude Code):

claude mcp add buggazi -- npx -y buggazi

solid

“12 worked examples; short of deep on per-tool docs and a stated limitation; read with 1 linked doc(s)”

This grade is wrong ›

tashan score: 60.0
Instruction depth: 67.0 (solid — documents the job properly, with examples you could follow)
Adoption: 507/wk
Upkeep: 69.0
Freshness: 87.0
Evidence coverage: 100% of the inputs this score can use
Health: active
License: SEE LICENSE IN LICENSE

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

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-13 buggazi published 2.14.21, was 2.14.15 A new release is available.
2026-08-14 buggazi published 2.14.22, was 2.14.21 A new release is available.
2026-08-22 buggazi published 2.14.26, was 2.14.22 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 Buggazi 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-buggazi.svg)](https://tashan.sh/capability/pkg-buggazi.html)

npm ↗ · source ↗ · pkg:buggazi

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?