integram-mcp@0.7.146
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 pull changes from an enclosing checkout’s configured remote without a separate confirmation, creating a real but conditional code-update risk. The source does not establish a package-controlled remote or an install-time trigger, so this supports a warning rather than a block.
Decision evidence
public snapshot- The package exposes index.js as its command and has no automatic install hook; prepublishOnly is the only lifecycle script shown.
- When the command starts, it runs the updater and schedules it hourly.
- The updater runs git pull from the package directory and, after a change, runs npm install and restarts the process.
- The cited runtime locations concern update checks and startup; they show no account action or account-action caller.
- The updater runs only when the command is launched, not as an npm install hook.
- The Git remote is configured outside the inspected code, so the source does not establish a package-controlled update destination.
Source & flagged code
3 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 · L2379Findings
Affected versions and remediation
This report applies to integram-mcp@0.7.146.
See all versions of integram-mcp for other recorded verdicts.
- Review the evidence and your use of integram-mcp@0.7.146 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.