integram-mcp@0.7.69
MCP server for Integram — connect AI assistants to your workspace via Model Context Protocol
AI Security Review
scanned 25d ago · by lpm-firewall-aiAutomatic Git pulling followed by npm installation is an unnecessary remote-update execution path. It is conditional on a Git checkout and lacks evidence of a specific malicious payload, so a warning is appropriate rather than a block.
Decision evidence
public snapshot- The package exposes index.js as its executable and has no registry install lifecycle hook.
- Running the executable enters main automatically.
- Main starts the automatic update routine immediately and schedules it hourly.
- The update routine pulls the configured Git remote and runs npm install after a changed revision.
- The automatic update path first requires the installed directory to be a Git repository.
- Authentication requests are sent to the configured Integram base URL with an in-memory token.
Source & flagged code
3 flagged · loading sourcePackage source invokes a package manager install command at runtime.
index.jsView on unpkg · L3056The package exposes index.js as its executable and has no registry install lifecycle hook.
Findings
Affected versions and remediation
This report applies to integram-mcp@0.7.69.
See all versions of integram-mcp for other recorded verdicts.
- Review the evidence and your use of integram-mcp@0.7.69 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.