integram-mcp@0.7.150
MCP server for Integram — connect AI assistants to your workspace via Model Context Protocol
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe manifest has no consumer install hook, and the flagged package-manager command is limited to the Git-based update path. The account-action hints point to update-check and CLI startup code, not automatic account changes.
Decision evidence
public snapshot- package.json exposes index.js as the command and defines only test and prepublishOnly scripts, both running a version check.
- The flagged cache path belongs to the update checker, which honors opt-out variables and stores update metadata in the temporary directory.
- The updater and version check start when the CLI runs; the entrypoint starts the server only when invoked as the program.
- The version checker fetches package dist-tags from the configured npm registry; it does not install an update.
- The Git updater requires a Git checkout, uses fast-forward-only pulls, and runs npm install only after the checkout changes; errors such as a missing Git repository are skipped.
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.150.
See all versions of integram-mcp for other recorded verdicts.
- Review the evidence and your use of integram-mcp@0.7.150 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.