arcroom@0.1.0
AI Security Review
scanned 6d ago · by lpm-firewall-aiRuntime hooks send the machine hostname to ArcRoom's API, but the README's detailed upload disclosure does not mention it. The service destination and team-tracking purpose are consistent with the package, so this is an undisclosed telemetry concern rather than clear malicious behavior.
Decision evidence
public snapshot- Each runtime event includes the machine hostname and working directory.
- The hook queues events containing those fields, and the daemon uploads event batches.
- The default upload endpoint is api.arcroomai.com.
- The README discloses several categories of uploaded activity data but does not mention the machine hostname.
- The runtime collection is activated by the agent hooks configured by `arcroom init`.
- The hostname is sent to ArcRoom's own API, and identifying machines may support the package's shared team run tracking.
- The README describes uploads of prompts, paths, commands, and other activity data, and provides an `arcroom off` command.
- The only lifecycle script is `prepublishOnly`, which runs the build and tests.
Source & flagged code
5 flaggedSource collects local host identity data and sends it to an external endpoint.
dist/home.jsView on unpkg · L11Findings
Affected versions and remediation
This report applies to arcroom@0.1.0.
See all versions of arcroom for other recorded verdicts.
- Review the evidence and your use of arcroom@0.1.0 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.