arcroom@0.0.5-beta
Shared team memory and run control for coding agents: Claude Code, Codex, Cursor, OpenCode
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe entry point runs the requested command, and agent settings are changed through the explicit init flow. Runtime event collection is disclosed as the package’s shared-memory function and is sent to the ArcRoom API.
Decision evidence
public snapshot- The only lifecycle script is prepublishOnly, which builds and tests; the entry point dispatches actions based on a command the user supplied.
- Agent configuration changes are performed by the explicit init command; laptop-wide hooks require the explicit --everywhere option.
- The default API is api.arcroomai.com, and the client sends requests using the configured ArcRoom key.
- The README describes the runtime data collected and sent, including prompt excerpts, paths and shell commands, and states that file contents, tool output and edit diffs are not sent.
- The daemon uploads queued events to the ArcRoom ingest endpoint as part of the package’s shared-memory and run-recording function.
Source & flagged code
5 flaggedFindings
Affected versions and remediation
This report applies to arcroom@0.0.5-beta.
See all versions of arcroom for other recorded verdicts.
- Review the evidence and your use of arcroom@0.0.5-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.