registry / integram-mcp / 0.7.141
integram-mcp@0.7.141
MCP server for Integram — connect AI assistants to your workspace via Model Context Protocol
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe flagged runtime calls resolve to update checks and server startup. The manifest has no install lifecycle hook, and inspected account-related startup behavior only reads and logs notifications.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Launching the executable starts the server and its update checks.
Impact
No unauthorized account action, credential transfer, or harmful install hook was established.
Mechanism
The update notifier fetches the package's npm dist-tag and logs when a newer version exists. The Git updater runs in a Git checkout and installs dependencies only after a changed commit.
AI rationale
The flagged runtime calls resolve to update checks and server startup. The manifest has no install lifecycle hook, and inspected account-related startup behavior only reads and logs notifications.
Evidence
package.jsonindex.js
Network endpoints1
registry.npmjs.org
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes index.js as the executable and declares only test and prepublishOnly scripts; no install lifecycle hook is present.
- The flagged source range reads a local update-check cache; it does not perform an account action.
- Startup calls the update check and schedules it daily; the executable entrypoint starts main.
- The update check fetches this package's npm dist-tag and can be disabled with environment flags.
- Unread notifications are fetched and logged at startup; the inspected code does not modify account state.
- The Git updater requires a Git checkout and uses a fast-forward-only pull.
Evidence against
- The executable starts an hourly Git update check, which may pull repository changes and run npm install after a changed commit.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
3 flagged · loading sourceindex.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = integram-mcp@0.7.104
matchedIdentity = npm:aW50ZWdyYW0tbWNw:0.7.104
similarity = 0.750
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 unpkg2349L2350: import { execSync } from 'child_process';
L2351: import { realpathSync } from 'fs';
High
2377log(`Updated ${before.slice(0, 7)} → ${after.slice(0, 7)}, restarting...`);
L2378: try { execSync('npm install --omit=dev', { cwd: __dirname, stdio: 'ignore', timeout: 30000 }); } catch {}
L2379: // 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 · L2377Findings
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.141.
See all versions of integram-mcp for other recorded verdicts.
- Review the evidence and your use of integram-mcp@0.7.141 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.