integram-mcp@0.7.70
MCP server for Integram — connect AI assistants to your workspace via Model Context Protocol
AI Security Review
scanned 26d ago · by lpm-firewall-aiThe automatic Git pull and npm install create a meaningful unattended remote-update and command-execution capability. The source does not establish a concrete malicious payload or an install-time attack, so a warning is more proportionate than a block.
Static reason
One or more suspicious static signals were detected.
Trigger
Running the package command from a Git checkout.
Impact
A changed remote checkout can alter the local package and cause dependency lifecycle code to run without a separate update command.
Mechanism
It invokes Git to pull the configured remote and invokes npm install when the revision changes.
AI rationale
The automatic Git pull and npm install create a meaningful unattended remote-update and command-execution capability. The source does not establish a concrete malicious payload or an install-time attack, so a warning is more proportionate than a block.
Evidence
index.js
Decision evidence
public snapshotAI called this Suspicious at 86.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- The published command entrypoint is index.js and no install lifecycle hook is declared.
- When run from a Git checkout, the entrypoint executes a Git pull and then npm install after a changed revision.
- This update routine runs at startup and repeats every hour.
Evidence against
- The package metadata declares only test and prepublish scripts, not install-time hooks.
- The automatic updater is limited to the package directory and first checks that it is a Git repository.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
3 flagged · loading sourceindex.jsView file
3040L3041: import { execSync } from 'child_process';
L3042: import { realpathSync } from 'fs';
High
3056log(`Updated ${before.slice(0, 7)} → ${after.slice(0, 7)}, restarting...`);
L3057: try { execSync('npm install --omit=dev', { cwd: __dirname, stdio: 'ignore', timeout: 30000 }); } catch {}
L3058: // 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 · L3056package.jsonView file
19"bin": {
"integram-mcp": "./index.js"
},
"scripts": {
"test": "node scripts/check-versions.mjs",
"prepublishOnly": "node scripts/check-versions.mjs"
},
"files
Medium
Suspicious Lifecycle Evidence
The published command entrypoint is index.js and no install lifecycle hook is declared.
Findings
3 High4 Medium5 Low
HighChild Processindex.js
HighShell
HighRuntime Package Installindex.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumSuspicious Lifecycle Evidencepackage.json
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to integram-mcp@0.7.70.
See all versions of integram-mcp for other recorded verdicts.
- Review the evidence and your use of integram-mcp@0.7.70 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.