registry / @programinglive/dev-workflow-mcp-server / 1.13.8
@programinglive/dev-workflow-mcp-server@1.13.8
MCP server to enforce development workflow discipline
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe postinstall action creates only an empty workflow state file, consistent with the package's workflow tracking purpose. The flagged broader agent configuration changes are in a setup script that runs only when directly invoked.
Static reason
One or more suspicious static signals were detected.
Trigger
npm postinstall creates the state file; setup-stack runs only when directly invoked.
Impact
No attack impact identified; the state file supports the package's workflow tracking purpose.
Mechanism
Writes initial workflow state under the installation caller's project root. No harmful network or credential behavior was identified in the reviewed paths.
AI rationale
The postinstall action creates only an empty workflow state file, consistent with the package's workflow tracking purpose. The flagged broader agent configuration changes are in a setup script that runs only when directly invoked.
Evidence
.state/workflow-state.json
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall hook runs install.js, which creates a workflow state file in the consumer project.
- The generated state contains empty task details and false or empty workflow flags; it does not collect project contents.
- The script that edits OpenCode configuration is guarded to run only when invoked directly.
Evidence against
- Installation does write .state/workflow-state.json in the consumer project when it is absent.
- The package declares prepare and postinstall lifecycle scripts.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemShell
HighEntropyStringsUrlStrings
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, execFile as execFileCallback } from "child_process";
L2: import { existsSync } from "fs";
High
Findings
6 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
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
LowScripts Present
LowWeak Cryptofactory-client.js
Affected versions and remediation
This report applies to @programinglive/dev-workflow-mcp-server@1.13.8.
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.8 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.