@xorox-ai/agent@0.1.2
Connects a coding project to [XOROX](https://xorox.eu) — automatic engineering context for Cursor, plus on-demand access to your project's Specifications and Tasks.
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe package’s automatic install hook makes persistent changes to a foreign AI-agent control surface by registering both a Cursor hook and MCP server. This meets the policy threshold for blocking an unconsented install-time control-surface mutation.
Decision evidence
public snapshot- The package runs scripts/postinstall.js automatically through its postinstall lifecycle.
- The installer targets the consumer project’s .cursor/hooks.json and .cursor/mcp.json files.
- The installer adds a before-submit hook and writes an XOROX MCP server entry to Cursor configuration.
Source & flagged code
5 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgThe package runs scripts/postinstall.js automatically through its postinstall lifecycle.
package.jsonView on unpkg · L25Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @xorox-ai/agent@0.1.2.
See all versions of @xorox-ai/agent for other recorded verdicts.
- Avoid installing @xorox-ai/agent@0.1.2. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.