registry / integram-mcp / 0.7.154
integram-mcp@0.7.154
MCP server for Integram — connect AI assistants to your workspace via Model Context Protocol
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe scanner's install finding is not supported by package.json, which has no install lifecycle hook. However, index.js starts a Git updater on program launch and hourly; because it runs from the package directory without checking the repository root, it can pull into a containing project and run npm install when the checkout changes.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Starting the MCP server, with another check every hour, when the package directory resolves to a Git working tree.
Impact
A nested installation may cause an unattended pull into the enclosing project and an install of the package's dependencies.
Mechanism
The updater runs git pull --ff-only with the package directory as its working directory, without verifying that the Git root is the package repository.
AI rationale
The scanner's install finding is not supported by package.json, which has no install lifecycle hook. However, index.js starts a Git updater on program launch and hourly; because it runs from the package directory without checking the repository root, it can pull into a containing project and run npm install when the checkout changes.
Evidence
index.js
Network endpoints1
registry.npmjs.org
Decision evidence
public snapshotAI called this Suspicious at 86.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- package.json defines a bin and a prepublishOnly version check, but no install lifecycle hook.
- When run as a program, index.js starts the updater immediately and repeats it hourly. It runs git pull --ff-only from the package directory and, when the checkout changes, runs npm install and schedules process exit.
- Git can resolve an enclosing repository from a nested package directory, so the updater may pull changes into a consumer checkout without checking that the repository belongs to this package.
- Login and API requests use the configured Integram base URL; the access token is attached to those API requests. Startup checks read workspace notifications and memory from that service.
- Account-changing workspace operations are routed from explicit MCP tool calls; the delete path requests approval before sending its delete request.
Evidence against
- The git update is conditional on finding a Git repository and uses a fast-forward-only pull.
- No source inspected sends Integram credentials to the npm update-check endpoint.
Behavioral surface
Source & flagged code
3 flagged · loading sourceindex.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = integram-mcp@0.7.151
matchedIdentity = npm:aW50ZWdyYW0tbWNw:0.7.151
similarity = 0.600
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 unpkg2367L2368: import { execSync } from 'child_process';
L2369: import { realpathSync } from 'fs';
High
2395log(`Updated ${before.slice(0, 7)} → ${after.slice(0, 7)}, restarting...`);
L2396: try { execSync('npm install --omit=dev', { cwd: __dirname, stdio: 'ignore', timeout: 30000 }); } catch {}
L2397: // 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 · L2395Findings
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.154.
See all versions of integram-mcp for other recorded verdicts.
- Review the evidence and your use of integram-mcp@0.7.154 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.