@boomi/exosphere@8.1.4
A library of Web Components
AI Security Review
scanned 11h ago · by lpm-firewall-aiSource confirms an automatic postinstall change to the consumer’s project-level MCP configuration, with environment-variable opt-outs and a server belonging to this package. This is a first-party agent extension lifecycle risk; the inspected excerpts do not establish broader agent control, credential transfer, or malicious execution.
Decision evidence
public snapshot- package.json runs scripts/postinstall-mcp.js automatically after installation.
- The hook skips when either EXOSPHERE_SKIP_MCP or npm_config_exosphere_skip_mcp is set; otherwise it operates from the consumer project root.
- The hook targets the consumer project’s .mcp.json and configures this package’s MCP server.
- The hook writes or updates the Exosphere server entry during installation without an affirmative consent prompt.
- The configured server exposes Exosphere component and icon lookup tools over standard input and output.
- The hook has explicit environment-variable opt-outs and skips when the package is not installed under node_modules.
- The configured server is this package’s own MCP server; inspected tool registrations provide component and icon information.
Source & flagged code
12 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgPackage source references a known benign dynamic code generation pattern.
dist/components/json-editor/json-editor.jsView on unpkg · L1315Findings
Affected versions and remediation
This report applies to @boomi/exosphere@8.1.4.
See all versions of @boomi/exosphere for other recorded verdicts.
- Review the evidence and your use of @boomi/exosphere@8.1.4 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.