registry / @programinglive/dev-workflow-mcp-server / 1.11.0
@programinglive/dev-workflow-mcp-server@1.11.0
MCP server to enforce development workflow discipline
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe lifecycle hook’s inspected effect is limited to initializing workflow state. The broader OpenCode and project-agent configuration changes belong to an explicit setup command, and the inspected sources did not establish malicious behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Package installation triggers postinstall; the separate OpenCode setup runs only when its command is invoked.
Impact
No confirmed credential collection, unrelated data transfer, or unconsented agent-control mutation was found.
Mechanism
Postinstall creates a project-local state directory and file. The setup command registers the package’s local MCP server and plugins and creates AGENTS.md if absent.
AI rationale
The lifecycle hook’s inspected effect is limited to initializing workflow state. The broader OpenCode and project-agent configuration changes belong to an explicit setup command, and the inspected sources did not establish malicious behavior.
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest’s postinstall runs install.js, which creates only a project-local workflow state file and skips when the install directory is inside node_modules.
- OpenCode and project-agent configuration changes are in a setup command that runs when directly invoked; it registers the local MCP server and plugins, and creates AGENTS.md only if absent.
- The runtime uses the MCP SDK over stdio; inspected dependency sources show protocol/transport code, dotenv configuration, and a native SQLite installer.
- The remaining flagged shell and child-process uses are tied to explicit setup, git-hook preparation, or bundle verification.
Evidence against
- The package has postinstall and prepare lifecycle scripts, and setup-stack.js writes an AGENTS.md file and edits OpenCode configuration when its setup command is run.
- The inspected dependency manifests include a native SQLite install command; its source is prebuild installation or native compilation.
Behavioral surface
ChildProcessCryptoEnvironmentVars
Source & flagged code
9 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 } from "child_process";
L2: import { existsSync } from "fs";
High
Findings
1 Critical5 High4 Medium6 Low
CriticalPrevious Version Dangerous Deltascripts/verify-bundle.mjs
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
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumEnvironment Vars
MediumShips Build Helperscripts/setup-test-dbs.sh
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowWeak Cryptofactory-client.js
Affected versions and remediation
This report applies to @programinglive/dev-workflow-mcp-server@1.11.0.
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.11.0 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.