@programinglive/dev-workflow-mcp-server@1.12.1
MCP server to enforce development workflow discipline
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe project-wide agent instruction write occurs only through the explicit setup command and matches the package’s stated workflow-enforcement purpose. Because it changes broader agent instructions, classify it as a warning-level agent capability risk.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs the package's setup command.
Impact
The generated instructions can shape later agent behavior across the project.
Mechanism
It creates AGENTS.md in the target project if absent, with mandatory workflow directions for coding agents.
AI rationale
The project-wide agent instruction write occurs only through the explicit setup command and matches the package’s stated workflow-enforcement purpose. Because it changes broader agent instructions, classify it as a warning-level agent capability risk.
Evidence
package.jsonscripts/setup-stack.jsAGENTS.mdopencode.json
Network endpoints2
github.comopencode.ai
Decision evidence
public snapshotAI called this Suspicious at 87.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The explicit setup command writes a project-root AGENTS.md when one is absent.
- The generated AGENTS.md directs coding agents to use this package’s mandatory workflow tools.
Evidence against
- The postinstall hook creates only a .state/workflow-state.json file in the invoking project.
- The AGENTS.md write is performed by the separately named setup command, not by the postinstall hook.
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 } 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.12.1.
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.12.1 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.