@xorox-ai/agent@0.1.6
Connects a coding project to [XOROX](https://xorox.eu) — automatic engineering context for Cursor and Claude Code, plus on-demand access to your project's Specifications and Tasks.
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe package performs automatic install-time setup of its own coding-agent integrations, creating a real agent extension lifecycle risk. The inspected behavior is consistent with package-owned XOROX integration, so warn rather than block.
Decision evidence
public snapshot- The install hook runs scripts/postinstall.js, which automatically installs Cursor and Claude Code hooks and MCP entries.
- The installer writes package-owned integrations into Cursor and Claude project configuration; the Claude prompt hook returns fetched XOROX context as additionalContext.
- The hook sends the XOROX project token to the configured XOROX API, whose default host is api.xorox.eu; the Claude installer retains unrelated hook groups.
- The registered commands point to this package’s own hook and MCP files, and the network request uses the XOROX project API.
- The Claude hook installer preserves unrelated hook groups. These facts support package-owned integration, but do not remove the install-time configuration change.
Source & flagged code
7 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgSource creates an unconsented AI-agent control surface through install-time mutation or a default unauthenticated remote skill channel.
Findings
Affected versions and remediation
This report applies to @xorox-ai/agent@0.1.6.
See all versions of @xorox-ai/agent for other recorded verdicts.
- Review the evidence and your use of @xorox-ai/agent@0.1.6 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.