registry / @programinglive/dev-workflow-mcp-server / 1.24.0
@programinglive/dev-workflow-mcp-server@1.24.0
MCP server to enforce development workflow discipline
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe automatic install behavior is limited to creating an initial local workflow state file, with no observed network contact, credential access, or unrelated action. The Husky hook skips outside a Git checkout, and the broader agent setup is gated behind an explicit command.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
npm install runs the postinstall hook; the separate stack configuration runs only when explicitly invoked.
Impact
The observed install-time effect is limited to creating a local workflow state file; no collection or transmission of data was found.
Mechanism
The postinstall creates .state/workflow-state.json in the npm caller’s project if absent. The inspected setup script modifies OpenCode configuration only when directly run.
AI rationale
The automatic install behavior is limited to creating an initial local workflow state file, with no observed network contact, credential access, or unrelated action. The Husky hook skips outside a Git checkout, and the broader agent setup is gated behind an explicit command.
Evidence
.state/workflow-state.json
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall hook runs install.js, which initializes a workflow state file in the npm caller’s project and skips when installed inside node_modules.
- The inspected install.js only creates the initial .state/workflow-state.json when it does not already exist; it contains no network or credential collection behavior.
- The prepare script skips Husky setup when the package is not in a Git checkout.
- The added project search code requires a project root that is the Git repository root and filters sensitive paths.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
11 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 unpkgsearch-project.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @programinglive/dev-workflow-mcp-server@1.23.11
matchedIdentity = npm:[redacted]:1.23.11
similarity = 0.930
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
Findings
1 Critical6 High6 Medium6 Low
CriticalPrevious Version Dangerous Deltasearch-project.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processsearch-project.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/verify-orphan-cleanup.sh
Affected versions and remediation
This report applies to @programinglive/dev-workflow-mcp-server@1.24.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.24.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.