@boomi/exosphere@8.1.1
A library of Web Components
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe install hook modifies Claude Code's project MCP configuration without prompting, but it registers this package's own server and provides an explicit environment-variable opt-out. Under the agent integration policy, this warrants a warning rather than a block.
Decision evidence
public snapshot- package.json runs scripts/postinstall-mcp.js automatically after installation.
- The postinstall script can be skipped with either of two environment variables; otherwise it targets the consumer project's .mcp.json and registers this package's MCP server.
- The script writes the registration into .mcp.json and replaces an existing Exosphere entry; this is first-party package-owned agent setup.
- The MCP server starts over standard input/output when invoked.
- Inspected avatar and React output show bundled component and React library code; no attack behavior was identified in those excerpts.
- The setup hook does not ask for consent; the opt-out requires a user-configured environment variable. It changes the consumer's agent configuration during installation.
Source & flagged code
7 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgPackage source references a known benign dynamic code generation pattern.
dist/components/rich-input-suggestion/rich-input-suggestion.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @boomi/exosphere@8.1.1.
See all versions of @boomi/exosphere for other recorded verdicts.
- Review the evidence and your use of @boomi/exosphere@8.1.1 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.