integram-mcp@0.7.71
MCP server for Integram — connect AI assistants to your workspace via Model Context Protocol
AI Security Review
scanned 25d ago · by lpm-firewall-aiNo install-time malware or credential-exfiltration path was found, but automatic unverified Git updates followed by npm installation are a concrete unsafe execution capability. The behavior warrants a warning rather than a publication block because it is limited to Git-checkout execution and lacks evidence of a package-controlled malicious recipient.
Decision evidence
public snapshot- The executable automatically checks whether its own directory is a Git repository, pulls its configured remote, and compares revisions.
- When a pull changes the revision, it runs npm install and exits for restart.
- The update routine runs on program startup and then every hour.
- The package metadata has no npm install lifecycle hook; its listed scripts are test and prepublish-only.
- The automatic update path is limited to executions from a Git checkout.
Source & flagged code
3 flagged · loading sourcePackage source invokes a package manager install command at runtime.
index.jsView on unpkg · L3063The executable automatically checks whether its own directory is a Git repository, pulls its configured remote, and compares revisions.
Findings
Affected versions and remediation
This report applies to integram-mcp@0.7.71.
See all versions of integram-mcp for other recorded verdicts.
- Review the evidence and your use of integram-mcp@0.7.71 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.