integram-mcp@0.7.16
MCP server for Integram — connect AI assistants to your workspace via Model Context Protocol
AI Security Review
scanned 25d ago · by lpm-firewall-aiThe automatic pull-and-install behavior is an active, conditional remote code supply path unrelated to ordinary MCP request handling. It warrants a warning, but the Git-repository guard and absence of an install lifecycle hook do not establish malicious install-time behavior in this release.
Decision evidence
public snapshot- The executable entry point is index.js and package scripts contain no install lifecycle hook.
- At program startup, the code immediately runs an automatic update check and schedules it hourly.
- When its installed directory is a Git repository, the updater pulls from its configured remote without user interaction.
- After a changed pull, the updater runs npm install in the package directory, which can run dependency lifecycle code.
- The automatic update path is conditional on the package directory being a Git repository.
- The inspected manifest has no preinstall, install, or postinstall script.
Source & flagged code
3 flagged · loading sourcePackage source invokes a package manager install command at runtime.
index.jsView on unpkg · L2166The executable entry point is index.js and package scripts contain no install lifecycle hook.
package.jsonFindings
Affected versions and remediation
This report applies to integram-mcp@0.7.16.
See all versions of integram-mcp for other recorded verdicts.
- Review the evidence and your use of integram-mcp@0.7.16 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.