Programinglive Dev Workflow MCP Server
@programinglive/dev-workflow-mcp-server
npm
v1.8.1
Source verified
Published by programinglive — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
MCP server to enforce development workflow discipline
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 − 1.2 = 99. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −1.2 | Package runs install-time scripts MTC-SUP-010 | supply-chain |
2. Client adoption risk — 99 − 6 = 93. 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.
Findings 13
high Shell/command execution in server code (exec.js)MTC-SRC-002
In the server's implementation (`exec.js:1`): 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: as execCallback } from "child_process"; import { existsSync } from "fs"; import path from "path"; import { fileURLToPath
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 exec.js
high Shell/command execution in server code (git-helpers.js)MTC-SRC-002
In the server's implementation (`git-helpers.js:5`): 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: onst { stdout } = await exec("git status --porcelain"); return stdout .split("\n") .filter(Boolean)
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 git-helpers.js
high Shell/command execution in server code (release-wrapper.js)MTC-SRC-002
In the server's implementation (`release-wrapper.js:3`): 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: rt { spawn } from 'node:child_process'; import fs from 'node:fs/promises'; import path from 'node:path'; import { resolv
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 release-wrapper.js
medium Hardcoded egress to an external endpoint (web/components/Hero.tsx)MTC-SRC-003
In the server's implementation (`web/components/Hero.tsx:14`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ly from npm API fetch("https://api.npmjs.org/downloads/point/last-month/@programinglive/dev-workflow-mcp-server"
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 web/components/Hero.tsx
low Shell/command execution in packaging/dev tooling (scripts/release.cjs)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/release.cjs:3`): 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 } = require('child_process'); const fs = require('fs'); const path = require('path'); const { updateReleaseN
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 scripts/release.cjs
low Shell/command execution in packaging/dev tooling (scripts/release.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/release.js:3`): 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 } = require('child_process'); const fs = require('fs'); const path = require('path'); const { updateReleaseN
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 scripts/release.js
low Shell/command execution in packaging/dev tooling (tests/build.test.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/build.test.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: as execCallback } from 'child_process'; import { promisify } from 'util'; import path from 'path'; const exec = promisi
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 tests/build.test.js
low Shell/command execution in packaging/dev tooling (tests/env-support.test.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/env-support.test.js:6`): 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: ort { exec } from "node:child_process"; import { promisify } from "node:util"; import { pathToFileURL } from "node:url";
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 tests/env-support.test.js
low Shell/command execution in packaging/dev tooling (tests/exec.test.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/exec.test.js:10`): 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: onst { stdout } = await exec(echoCommand); const normalized = stdout.trim().replace(/^"(.*)"$/, '$1'); assert.strict
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 tests/exec.test.js
low Shell/command execution in packaging/dev tooling (tests/hello-world.test.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/hello-world.test.js:3`): 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: { execSync } from 'node:child_process'; import path from 'node:path'; import { fileURLToPath } from 'node:url'; const _
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 tests/hello-world.test.js
low Shell/command execution in packaging/dev tooling (tests/release-wrapper.test.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/release-wrapper.test.js:7`): 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: rt { spawn } from "node:child_process"; const __filename = fileURLToPath(import.meta.url); const __dirname = path.dirna
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 tests/release-wrapper.test.js
low Dynamic module load from a non-literal in packaging/dev tooling (tests/workflowState.test.js)MTC-SRC-005
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/workflowState.test.js:122`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: WorkflowState } = await import(moduleUrl.href); const state = new TempWorkflowState(stateFile); await state.load();
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 tests/workflowState.test.js
low Package runs install-time scripts (postinstall)MTC-SUP-010
"@programinglive/dev-workflow-mcp-server" executes postinstall script(s) at install time. An install hook runs at install time; most are routine build/setup, but review what it does before trusting it.
Evidence: node install.js
Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.
Location: package @programinglive/dev-workflow-mcp-server
Tools 2
Each tool and what it can reach — statically extracted from the published source.
pre_commit_checklistno sensitive capabilityworkflow_reminderno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (2 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan 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 |
|---|---|---|---|---|
v1.8.1 latest |
A 93/100 | 13 | 1.13.0 | 2026-09-09 |
Embed this score
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.
Verify this score yourself
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 @programinglive/dev-workflow-mcp-server --onlineOther implementations of Programinglive Dev Workflow 1
Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →
More in Developer Tools
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.