integram-mcp@0.7.169
MCP server for Integram — connect AI assistants to your workspace via Model Context Protocol
AI Security Review
scanned 2h ago · by lpm-firewall-aiThe source establishes an automatic Git update path that can install dependencies and restart the program, creating a real but checkout-dependent execution risk. The inspected login path sends credentials to the configured Integram service, and the manifest has no install hook; the evidence supports a warning rather than a block.
Decision evidence
public snapshot- package.json defines a command-line entry point and has no install lifecycle hook.
- When the program starts, it runs an automatic update check and repeats it hourly.
- For a Git checkout, the updater pulls from its configured remote and runs npm install if the checkout changes, then schedules a restart.
- Login sends the configured credentials to the configured Integram base URL.
- The update check and update commands are package runtime behavior, not install-time execution.
- The inspected login path targets the configured Integram service; no unrelated credential recipient was identified.
Source & flagged code
4 flagged · loading sourcePackage source invokes a package manager install command at runtime.
index.jsView on unpkg · L2453Source file is highly similar to a previously finalized malicious package; route for source-aware review.
index.jsView on unpkgFindings
Affected versions and remediation
This report applies to integram-mcp@0.7.169.
See all versions of integram-mcp for other recorded verdicts.
- Review the evidence and your use of integram-mcp@0.7.169 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.