integram-mcp@0.7.136
MCP server for Integram — connect AI assistants to your workspace via Model Context Protocol
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe runtime updater can install and execute upstream changes without separate approval when the command runs from a Git checkout. The source shows a deliberate update mechanism but does not establish malicious content or a package-selected remote, so this warrants a warning rather than a block.
Decision evidence
public snapshot- The manifest exposes index.js as the command and defines only a prepublishOnly version check; it has no install hook.
- When the command starts, it checks whether its directory is a Git checkout and attempts to update it.
- After an upstream change, it runs a production dependency install; the updater also runs at startup and hourly, and the command starts it only when executed as a program.
- The updater skips when Git checks fail, and the package manifest contains no install-time lifecycle hook.
- The inspected updater uses the checkout’s configured Git remote; no package-selected update host or separate malicious payload was established.
Source & flagged code
4 flagged · loading sourceThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
index.jsView on unpkgPackage source invokes a package manager install command at runtime.
index.jsView on unpkg · L3268Findings
Affected versions and remediation
This report applies to integram-mcp@0.7.136.
See all versions of integram-mcp for other recorded verdicts.
- Review the evidence and your use of integram-mcp@0.7.136 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.