registry / integram-mcp / 0.7.158
integram-mcp@0.7.158
MCP server for Integram — connect AI assistants to your workspace via Model Context Protocol
AI Security Review
scanned 9h ago · by lpm-firewall-aiThe runtime updater can change the checkout and install dependencies without a prompt, so it presents a real unresolved risk. The inspected source does not establish malicious update content, credential exfiltration, or unrequested account actions.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Launching the package command; the updater then repeats hourly.
Impact
A remote update can change the checkout and trigger dependency installation while the server is running.
Mechanism
It runs Git pull in the package directory and runs npm install there after a revision change, without asking the user first.
AI rationale
The runtime updater can change the checkout and install dependencies without a prompt, so it presents a real unresolved risk. The inspected source does not establish malicious update content, credential exfiltration, or unrequested account actions.
Evidence
index.jspackage.json
Decision evidence
public snapshotAI called this Suspicious at 82.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The manifest exposes index.js as the command and lists only a prepublishOnly script; it has no install hook.
- Running the command starts a Git updater immediately and schedules it to repeat hourly.
- When the package directory is inside a Git worktree, the updater pulls its configured remote and, if the revision changes, runs npm install in that directory.
- Login sends the environment-supplied credentials to the configured service URL; the inspected source shows no separate credential recipient.
- The scanner-labeled account location resolves to a temporary update-cache path; workspace deletion is initiated through an MCP tool and requires explicit confirmation.
Evidence against
- The updater uses the worktree’s configured Git remote, and the inspected source does not establish a malicious remote or payload.
- The source does not show automatic publisher-selected account changes or credential forwarding to a separate recipient.
Behavioral surface
ChildProcessEnvironmentVarsFilesystem
Source & flagged code
3 flagged · loading sourceindex.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = integram-mcp@0.7.156
matchedIdentity = npm:aW50ZWdyYW0tbWNw:0.7.156
similarity = 0.667
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
index.jsView on unpkg2380L2381: import { execSync } from 'child_process';
L2382: import { realpathSync } from 'fs';
High
2408log(`Updated ${before.slice(0, 7)} → ${after.slice(0, 7)}, restarting...`);
L2409: try { execSync('npm install --omit=dev', { cwd: __dirname, stdio: 'ignore', timeout: 30000 }); } catch {}
L2410: // Allow pending responses to drain before exit
High
Runtime Package Install
Package source invokes a package manager install command at runtime.
index.jsView on unpkg · L2408Findings
1 Critical3 High3 Medium5 Low
CriticalPrevious Version Dangerous Deltaindex.js
HighChild Processindex.js
HighShell
HighRuntime Package Installindex.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to integram-mcp@0.7.158.
See all versions of integram-mcp for other recorded verdicts.
- Review the evidence and your use of integram-mcp@0.7.158 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.