integram-mcp@0.7.77
MCP server for Integram — connect AI assistants to your workspace via Model Context Protocol
AI Security Review
scanned 25d ago · by lpm-firewall-aiAutomatic Git pulling followed by npm installation is an unsafe self-update capability. It is not an npm lifecycle attack and only activates for a Git checkout, so a warning is proportionate.
Static reason
One or more suspicious static signals were detected.
Trigger
A user runs the package command from a Git checkout.
Impact
A compromised or untrusted configured Git remote could cause unreviewed code and dependency lifecycle execution.
Mechanism
On startup and hourly, it runs git pull against the checkout's configured remote; if changed, it runs npm install in the package directory.
AI rationale
Automatic Git pulling followed by npm installation is an unsafe self-update capability. It is not an npm lifecycle attack and only activates for a Git checkout, so a warning is proportionate.
Evidence
index.js
Decision evidence
public snapshotAI called this Suspicious at 90.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- The executable automatically pulls its enclosing Git repository and runs npm install after a changed revision.
- The update routine runs at startup and then every hour.
- The package exposes index.js as its command-line entrypoint.
Evidence against
- Package metadata contains no npm install lifecycle hook.
- The automatic updater first requires the installed directory to be a Git repository; no configured remote was present in inspected source.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
3 flagged · loading sourceindex.jsView file
3092L3093: import { execSync } from 'child_process';
L3094: import { realpathSync } from 'fs';
High
3108log(`Updated ${before.slice(0, 7)} → ${after.slice(0, 7)}, restarting...`);
L3109: try { execSync('npm install --omit=dev', { cwd: __dirname, stdio: 'ignore', timeout: 30000 }); } catch {}
L3110: // 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 · L31083105execSync('git pull --ff-only', { cwd: __dirname, stdio: 'ignore', timeout: 15000 });
const after = execSync('git rev-parse HEAD', { cwd: __dirname, encoding: 'utf8' }).trim();
if (before !== after) {
log(`Updated ${before.slice(0, 7)} → ${after.slice(0, 7)}, restarting...`);
try { execSync('npm install --omit=dev', { cwd: __dirname, stdio: 'ignore', timeout: 30000 }); } catch {}
// Allow pending responses to drain before exit
log('Shutting down gracefully...');
Medium
Ai Review Evidence
The executable automatically pulls its enclosing Git repository and runs npm install after a changed revision.
index.jsFindings
3 High4 Medium5 Low
HighChild Processindex.js
HighShell
HighRuntime Package Installindex.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumAi Review Evidenceindex.js
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to integram-mcp@0.7.77.
See all versions of integram-mcp for other recorded verdicts.
- Review the evidence and your use of integram-mcp@0.7.77 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.