arcroom@0.0.2-beta
Shared team memory and run control for coding agents: Claude Code, Codex, Cursor, OpenCode
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe agent-configuration writes are triggered by the user’s explicit `arcroom init` command and configure ArcRoom’s project integration. Runtime requests send the saved key to the configured ArcRoom API, while the README discloses the collected data and an off switch; no malicious behavior was identified.
Decision evidence
public snapshot- The CLI runs initialization only when the user invokes the `init` command.
- Initialization configures ArcRoom hooks and writes agent settings for the current project.
- The client sends its saved API key as a bearer token to the configured API; the default host is `api.arcroomai.com`.
- The README discloses the prompt and activity data collected by the hooks, says file contents and tool output are not sent, and documents an `off` command.
- The manifest has a `prepublishOnly` script, which is not an install lifecycle hook.
- The flagged agent-configuration writes are part of the documented, explicitly invoked setup command.
Source & flagged code
5 flaggedManifest-trigger-reachable source writes behavior-bearing configuration into a user or project AI-agent control surface.
Findings
Affected versions and remediation
This report applies to arcroom@0.0.2-beta.
See all versions of arcroom for other recorded verdicts.
- Review the evidence and your use of arcroom@0.0.2-beta 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.