registry / @programinglive/dev-workflow-mcp-server / 1.13.15
@programinglive/dev-workflow-mcp-server@1.13.15
MCP server to enforce development workflow discipline
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe install-time behavior is limited to creating the package’s workflow state file in the invoking project. The flagged setup, shell, and git capabilities are consistent with the package’s stated workflow and development tooling purpose; the reviewed source showed no malicious data collection or unrelated transmission.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
npm postinstall creates a project workflow-state file; setup and repository actions require explicit commands or tool calls.
Impact
A workflow state file may be added to the invoking project during installation.
Mechanism
The install hook writes initial workflow state. The reviewed paths showed no automatic credential collection or unrelated network transmission.
AI rationale
The install-time behavior is limited to creating the package’s workflow state file in the invoking project. The flagged setup, shell, and git capabilities are consistent with the package’s stated workflow and development tooling purpose; the reviewed source showed no malicious data collection or unrelated transmission.
Evidence
.state/workflow-state.json
Decision evidence
public snapshotAI called this Clean at 88.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall hook runs install.js, which creates an initial .state/workflow-state.json in the invoking project unless that file already exists.
- The install script uses INIT_CWD or the current directory and skips state creation when the path is inside node_modules.
- The setup script writes AGENTS.md as part of an explicit setup operation; it is not called by the postinstall hook.
- The commit handler checks workflow readiness before staging changes, and commit/push occurs through that handler.
Evidence against
- The postinstall hook does make a project-level filesystem change by creating .state/workflow-state.json.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemShell
HighEntropyStringsUrlStrings
Source & flagged code
10 flaggedpackage.jsonView file
•scripts.postinstall = node install.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node install.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgexec.jsView file
1import { exec as execCallback, execFile as execFileCallback } from "child_process";
L2: import { existsSync } from "fs";
High
Findings
1 Critical6 High4 Medium6 Low
CriticalPrevious Version Dangerous Deltatools/handler-modules/commit-handlers.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processexec.js
HighShellscripts/install-husky.js
HighSandbox Evasion Gated Capabilityscripts/setup-stack.js
HighRuntime Package Installscripts/setup-stack.js
HighSemantic Analysis Limitedexec.js#virtual:normalized:round1
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumEnvironment Vars
MediumShips Build Helperscripts/setup-test-dbs.sh
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
Affected versions and remediation
This report applies to @programinglive/dev-workflow-mcp-server@1.13.15.
See all versions of @programinglive/dev-workflow-mcp-server for other recorded verdicts.
- Review the evidence and your use of @programinglive/dev-workflow-mcp-server@1.13.15 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.