registry / integram-mcp / 0.7.130
integram-mcp@0.7.130
MCP server for Integram — connect AI assistants to your workspace via Model Context Protocol
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe manifest has no install-time hook. The only notable execution primitive is a conditional Git update for the launched CLI, with dependency installation only after a changed checkout; inspected source establishes no concrete attack behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The CLI starts when invoked; its Git updater runs at startup and on an hourly timer.
Impact
No concrete malicious effect was established; the manifest has no install hook and the update behavior is limited to the launched CLI.
Mechanism
The updater checks the current Git checkout and pulls fast-forward changes; it installs dependencies only if the checkout changes.
AI rationale
The manifest has no install-time hook. The only notable execution primitive is a conditional Git update for the launched CLI, with dependency installation only after a changed checkout; inspected source establishes no concrete attack behavior.
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 CLI and defines only a prepublishOnly version-check command; no install lifecycle hook is declared.
- The CLI’s updater checks the on-disk package version and Git state; it runs npm install only after a fast-forward pull changes the checkout, then restarts.
- The flagged line 189 is an update-check cache read under the OS temporary directory.
- Startup calls the update checker; the other flagged locations are its scheduled call and the CLI’s fatal-error handler.
- The update check defaults to the npm registry and can be disabled with environment variables.
Evidence against
- When run from a Git checkout, the CLI can pull its configured remote 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 unpkg3203L3204: import { execSync } from 'child_process';
L3205: import { realpathSync } from 'fs';
High
3231log(`Updated ${before.slice(0, 7)} → ${after.slice(0, 7)}, restarting...`);
L3232: try { execSync('npm install --omit=dev', { cwd: __dirname, stdio: 'ignore', timeout: 30000 }); } catch {}
L3233: // 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 · L3231Findings
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.130.
See all versions of integram-mcp for other recorded verdicts.
- Review the evidence and your use of integram-mcp@0.7.130 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.