arcy.js@0.4.0
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 12d ago · by lpm-firewall-aiThe source ties the flagged callback to ARCY’s own widget telemetry, with bounded measurement collection when consent is absent. The manifest has no install hook, and the stage entrypoint uses an offline fetch stub.
Decision evidence
public snapshot- package.json exposes the runtime entrypoints and defines only a prepublishOnly release check and build hook.
- The runtime POST batches event data to ARCY’s telemetry API using the SDK token and omitting browser credentials.
- Without consent, collection is limited to an event allowlist and is disabled when Do Not Track or Global Privacy Control is signaled; field descriptions use element metadata rather than entered values.
- The stage helper injects an offline fetch with fixture responses and a synthetic session token.
- The declared LiquidJS and Marked dependencies use template and Markdown parser entrypoints; their inspected manifests show build and test scripts.
Source & flagged code
6 flaggedA manifest entrypoint or package-local install chain reaches a fixed external POST callback.
Findings
Affected versions and remediation
This report applies to arcy.js@0.4.0.
See all versions of arcy.js for other recorded verdicts.
- Review the evidence and your use of arcy.js@0.4.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.