registry / @programinglive/dev-workflow-mcp-server / 1.13.0
@programinglive/dev-workflow-mcp-server@1.13.0
MCP server to enforce development workflow discipline
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe declared lifecycle scripts have bounded setup behavior: postinstall creates a workflow-state file, and prepare skips Husky installation when the package is not in a Git checkout. The agent configuration writes and plugin registration are part of an explicit setup command, and the inspected runtime shows no concrete attack behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
Package installation runs the declared prepare and postinstall scripts; the broader OpenCode setup requires running the setup command.
Impact
No confirmed harmful effect; the inspected changes support the package’s workflow and agent setup functions.
Mechanism
Postinstall creates a workflow state file. Prepare skips Husky setup outside a Git checkout. The explicit setup flow registers the workflow server and plugin and may create AGENTS.md when absent.
AI rationale
The declared lifecycle scripts have bounded setup behavior: postinstall creates a workflow-state file, and prepare skips Husky installation when the package is not in a Git checkout. The agent configuration writes and plugin registration are part of an explicit setup command, and the inspected runtime shows no concrete attack behavior.
Evidence
package.jsoninstall.jsscripts/install-husky.jsscripts/setup-stack.jsexec.js
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The install hooks are declared in package.json; postinstall creates a project workflow-state file, and prepare skips Husky setup outside a Git checkout.
- The OpenCode and AGENTS.md setup runs through an explicit setup command and configures the package’s workflow server and plugin.
- The runtime entrypoint starts an MCP server over standard input and output using the MCP SDK.
- The command helper selects a project Git repository and rejects using the package repository as the fallback target.
- The inspected SQLite and dotenv dependency sources show native build setup and environment-file loading.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemShell
HighEntropyStringsUrlStrings
Source & flagged code
8 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
5 High4 Medium6 Low
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
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to @programinglive/dev-workflow-mcp-server@1.13.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.13.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.