io.github.jyswee/buggazi
NPM · BUGGAZI · 2 COMPONENTS · SCANNED AUG 3
Project management for coding agents. Bugs, features, sprints. 73 tools, stdio or remote SSE.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security55
- Malware check failed: a supply-chain vendor flagged a high-severity malware risk. See how to fix → Fail
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (SEE LICENSE IN LICENSE) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 159 tokens (~79/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · buggazi
claude mcp add jyswee-buggazi -- npx -y buggazi
codex mcp add jyswee-buggazi -- npx -y buggazi
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jyswee-buggazi": {
"type": "local",
"command": [
"npx",
"-y",
"buggazi"
],
"enabled": true
}
}
} openclaw mcp add jyswee-buggazi --command npx --arg -y --arg buggazi
mcp_servers:
jyswee-buggazi:
command: "npx"
args: ["-y", "buggazi"] {
"mcpServers": {
"jyswee-buggazi": {
"command": "npx",
"args": [
"-y",
"buggazi"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +4
- Stability: unverified → 0.23 ▲ functional
- 2 Aug 26 +1
- Malware scan: unverified → fail ▼ security
- Malware indicator gptMalware:Qbj-7t5tOb97ufO2iBw2JPLjXkGEtWgBAWIf60AV8_6A: high ▼ security
- Malware indicator gptMalware:QH1DdtMJCUIHElybo-UUbk8WWkVoMReGIMg-hVeRjZ4c: high ▼ security
- Malware indicator gptMalware:Qk36J5MOjxsfPl4eBJ_Zq4EgoZ1C45-3CNWLElPKUPbg: high ▼ security
- 31 Jul 26 −11
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 +32
- Tool coverage: unverified → 100 ▲ functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: pass functional
- First check of Schema quality: fail functional
- First check of Schema quality: good functional
- 26 Jul 26 26
First indexed and scored.
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 0 packages
0 packages in the resolved dependency tree.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
buggazi_get_started ~32
Explains what Buggazi is and how to activate this MCP server (no API key configured yet).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
buggazi_signup ~127
Create a new Buggazi tenant. Requires the human's email: the activation link is emailed to them (card required via Stripe, nothing charged during the 7-day free trial). Returns an API key (auto-saved to ./.bgz/config.json) and unlocks all Buggazi tools immediately. Ask the human for their email before calling.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Human email. The activation link is sent here. | |
| name | string | — | Project display name (optional) |
| slug | string | yes | Short project slug, e.g. "my-app" |
No output schema declared.
No examples provided.