specky-sdd
npm
v3.13.0
Source verified
Published by paulasilvatech — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
Specky — Spec-Driven Development CLI toolkit. 58 MCP tools, 13 agents, 22 prompts, 14 skills, 16 hooks. Unified `specky` CLI installs to Claude Code, GitHub Copilot, Cursor, or OpenCode on macOS, Linux, and Windows.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 6 = 94. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
In the server's implementation (`dist/cli/commands/apm.js:12`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: spawnSync } from "node:child_process"; import { writeFileSync } from "node:fs"; import { resolve } from "node:path"; im
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/cli/commands/apm.js
In the server's implementation (`dist/cli/commands/hooks.js:4`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: spawnSync } from "node:child_process"; import { existsSync, readdirSync } from "node:fs"; import { resolve } from "node
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/cli/commands/hooks.js
Each tool and what it can reach — statically extracted from the published source.
sdd_create_prnetwork egresssdd_advance_phaseno sensitive capabilitysdd_amendno sensitive capabilitysdd_auto_pipelineno sensitive capabilitysdd_batch_importno sensitive capabilitysdd_batch_transcriptsno sensitive capabilitysdd_check_ecosystemno sensitive capabilitysdd_check_syncno sensitive capabilitysdd_checklistno sensitive capabilitysdd_checkpointno sensitive capabilitysdd_clarifyno sensitive capabilitysdd_compliance_checkno sensitive capabilitysdd_context_statusno sensitive capabilitysdd_create_branchno sensitive capabilitysdd_cross_analyzeno sensitive capabilitysdd_discoverno sensitive capabilitysdd_export_work_itemsno sensitive capabilitysdd_figma_to_specno sensitive capabilitysdd_generate_devcontainerno sensitive capabilitysdd_generate_dockerfileno sensitive capabilitysdd_generate_iacno sensitive capabilitysdd_generate_pbtno sensitive capabilitysdd_generate_testsno sensitive capabilitysdd_get_statusno sensitive capabilitysdd_get_templateno sensitive capabilitysdd_implementno sensitive capabilitysdd_import_documentno sensitive capabilitysdd_import_transcriptno sensitive capabilitysdd_initno sensitive capabilitysdd_list_checkpointsno sensitive capabilitysdd_metricsno sensitive capabilitysdd_model_routingno sensitive capabilitysdd_researchno sensitive capabilitysdd_restoreno sensitive capabilitysdd_run_analysisno sensitive capabilitysdd_scan_codebaseno sensitive capabilitysdd_setup_codespacesno sensitive capabilitysdd_setup_local_envno sensitive capabilitysdd_validate_earsno sensitive capabilitysdd_validate_iacno sensitive capabilitysdd_verify_tasksno sensitive capabilitysdd_verify_testsno sensitive capabilitysdd_write_bugfixno sensitive capabilitysdd_write_designno sensitive capabilitysdd_write_specno sensitive capabilitysdd_write_tasksno sensitive capabilityScan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v3.13.0 latest |
A 94/100 | 2 | 1.13.0 | 2026-09-09 |
v3.12.1 |
A 94/100 | 2 | 1.12.1 | 2026-08-10 |
v3.12.0 |
A 94/100 | 2 | 1.12.1 | 2026-08-07 |
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan specky-sdd --online
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.
A standalone MCP stdio bridge for Affinity by Canva's local MCP SSE server.