registry / @programinglive/dev-workflow-mcp-server / 1.13.16
@programinglive/dev-workflow-mcp-server@1.13.16
MCP server to enforce development workflow discipline
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe install hook creates a local workflow state file, while broader agent configuration changes occur through an explicitly invoked setup command. The reviewed server startup showed no automatic credential collection or unrelated network activity.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
npm lifecycle hooks create local workflow state; broader agent-stack setup runs only when the user invokes the setup command.
Impact
No automatic credential collection, unrelated network contact, or unauthorized account action was identified.
Mechanism
The postinstall hook initializes a project state file. Explicit setup registers the MCP server and related tools in OpenCode and creates AGENTS.md only if absent.
AI rationale
The install hook creates a local workflow state file, while broader agent configuration changes occur through an explicitly invoked setup command. The reviewed server startup showed no automatic credential collection or unrelated network activity.
Evidence
.state/workflow-state.jsonopencode.jsonAGENTS.md
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package entry point is index.js; its server initialization runs only when directly launched.
- The postinstall script creates a project-local .state/workflow-state.json file and skips this when installed inside node_modules.
- The broader OpenCode and AGENTS.md setup is performed by the explicit setup command.
Evidence against
- The package declares prepare and postinstall lifecycle scripts.
- The explicit setup command can modify OpenCode configuration and add an AGENTS.md file to the target project.
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 Deltaindex.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
Low
Affected versions and remediation
This report applies to @programinglive/dev-workflow-mcp-server@1.13.16.
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.16 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.