registry / @programinglive/dev-workflow-mcp-server / 1.19.7
@programinglive/dev-workflow-mcp-server@1.19.7
MCP server to enforce development workflow discipline
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe lifecycle scripts initialize local workflow state and set up repository hooks; configuration changes to OpenCode and AGENTS.md occur only through an explicitly run setup command. Monitoring can send project and task metadata, but it is disabled unless the user configures DEVWF_MONITOR_URL and is consistent with the package's workflow-monitoring purpose.
Static reason
One or more suspicious static signals were detected.
Trigger
npm postinstall initializes workflow state; monitoring reports during state saves only when DEVWF_MONITOR_URL is configured; agent setup requires direct script execution.
Impact
No malicious behavior identified. Enabling monitoring shares project paths, task descriptions, and workflow metadata with the configured service.
Mechanism
The install hook creates project workflow state. Optional monitoring posts workflow metadata to the configured endpoint. The explicit setup command registers the MCP server and updates agent configuration.
AI rationale
The lifecycle scripts initialize local workflow state and set up repository hooks; configuration changes to OpenCode and AGENTS.md occur only through an explicitly run setup command. Monitoring can send project and task metadata, but it is disabled unless the user configures DEVWF_MONITOR_URL and is consistent with the package's workflow-monitoring purpose.
Evidence
.state/workflow-state.jsonopencode.jsonAGENTS.md
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 the package's local state initializer.
- The initializer uses the installer's project directory and skips state creation when installing inside node_modules.
- Monitoring is disabled when DEVWF_MONITOR_URL is empty.
- When configured, monitoring sends project and task metadata to the configured URL; this matches the workflow-monitoring purpose.
- The setup script modifies agent configuration only when run directly.
Evidence against
- Monitoring includes identifying project paths and task descriptions, so users should understand what enabling it shares.
- The install hook writes a workflow state file in the installing project.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
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
6 High6 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
MediumDynamic Requiresecurity/log-bridge.cjs
MediumNetwork
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.19.7.
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.19.7 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.