arcroom@0.0.4-beta
Shared team memory and run control for coding agents: Claude Code, Codex, Cursor, OpenCode
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package’s documented runtime capture is core to its purpose and is enabled through an explicit setup command. However, its events also include the machine hostname, which the README does not disclose, so the telemetry merits a warning.
Decision evidence
public snapshot- Each recorded event includes the machine hostname and current working directory.
- A user prompt is added to the event payload.
- The daemon uploads queued events to ArcRoom’s ingest API.
- The README discloses prompts, paths, and other recorded fields, but does not mention hostname collection.
- The hooks are configured by running the explicit `arcroom init` command.
- The only lifecycle script is `prepublishOnly`, which builds and tests; there is no install hook.
- The README describes the runtime collection, secret redaction, and `arcroom off` control.
- The README says file contents, tool output, and edit diffs are not sent.
- The credential is sent to the package’s own ArcRoom API.
Source & flagged code
5 flaggedFindings
Affected versions and remediation
This report applies to arcroom@0.0.4-beta.
See all versions of arcroom for other recorded verdicts.
- Review the evidence and your use of arcroom@0.0.4-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.