arcy.js@0.6.1
ARCY, the universal JavaScript utility for embedding an AI agent that talks to, learns from, and acts on behalf of your users.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe flagged callback resolves to ARCY’s own API, but the SDK also collects and sends browser measurement events before consent unless the browser signals Do Not Track or Global Privacy Control. Because the README does not disclose this pre-consent behavior, this is suspicious runtime telemetry rather than a clear malicious attack.
Decision evidence
public snapshot- When consent has not been granted, the collector still starts if measurement is allowed by the browser’s privacy signals.
- Pre-consent measurement can include page loads, navigation, clicks, form submissions, and field interactions.
- Measurement events include the current route, locale, device class, and event payload.
- The measurement transport posts events to ARCY’s own API.
- The README describes the consent flow but does not disclose that measurement can occur before consent.
- Network traffic is directed to the package’s own ARCY API.
- The README provides a consent API and says refusal stops collection.
Source & flagged code
6 flaggedA manifest entrypoint or package-local install chain reaches a fixed external POST callback.
dist/index.cjsView on unpkgFindings
Affected versions and remediation
This report applies to arcy.js@0.6.1.
See all versions of arcy.js for other recorded verdicts.
- Review the evidence and your use of arcy.js@0.6.1 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.