integram-mcp@0.7.13
MCP server for Integram — connect AI assistants to your workspace via Model Context Protocol
AI Security Review
scanned 25d ago · by lpm-firewall-aiThe active self-updater creates a meaningful remote code execution risk in Git-based deployments. It does not meet the package lifecycle abuse criteria for blocking.
Static reason
One or more suspicious static signals were detected.
Trigger
Running the command from a Git checkout.
Impact
A compromised or untrusted configured Git remote could cause execution of newly pulled package code or dependency lifecycle code.
Mechanism
Startup and an hourly timer invoke Git pull; a changed revision causes npm installation before process exit.
AI rationale
The active self-updater creates a meaningful remote code execution risk in Git-based deployments. It does not meet the package lifecycle abuse criteria for blocking.
Evidence
index.js
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- The executable runs an automatic update check at startup and hourly.
- In a Git checkout, the updater pulls the configured remote and then runs npm installation when the revision changes.
- The manifest exposes index.js as the command entrypoint and has no install lifecycle hook.
Evidence against
- The updater first requires the package directory to be a Git repository, so normal registry installations do not meet its activation condition.
- No package install, preinstall, or postinstall hook is declared.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
3 flagged · loading sourceindex.jsView file
2138L2139: import { execSync } from 'child_process';
L2140: import { realpathSync } from 'fs';
High
2154log(`Updated ${before.slice(0, 7)} → ${after.slice(0, 7)}, restarting...`);
L2155: try { execSync('npm install --omit=dev', { cwd: __dirname, stdio: 'ignore', timeout: 30000 }); } catch {}
L2156: // 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 · L2154package.jsonView file
19"bin": {
"integram-mcp": "./index.js"
},
"scripts": {
"test": "node scripts/check-versions.mjs",
"prepublishOnly": "node scripts/check-versions.mjs
Medium
Suspicious Lifecycle Evidence
The manifest exposes index.js as the command entrypoint and has no install lifecycle hook.
package.jsonFindings
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.13.
See all versions of integram-mcp for other recorded verdicts.
- Review the evidence and your use of integram-mcp@0.7.13 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.