reflex-browser@0.12.0
Token-efficient browser automation for AI agents. Local MCP server + CLI: compressed page snapshots, batched actions, forensic failures.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe flagged primitives are disclosed, runtime-only browser-automation features; source inspection found no install hook, credential exfiltration, remote payload execution, or foreign agent-control-surface mutation. The scanner's exfiltration conclusion overstates the observed credit/auth API payloads.
Decision evidence
public snapshot- Runtime profile seeding copies Chrome cookie/login-data files on Windows/Linux into the package-owned browser profile.
- The MCP client sends limited trial/credit telemetry to the Reflex API after user runtime actions.
- package.json has no preinstall, install, or postinstall hook.
- Browser, profile, and MCP behavior is activated by the package CLI/MCP entrypoints, not installation.
- The first-call payload contains tool/result/client/device metadata, not page contents or browser credentials.
- Cross-origin browser fetch is blocked unless REFLEX_ALLOW_CROSS_ORIGIN_FETCH=1.
Source & flagged code
4 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/reflex.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to reflex-browser@0.12.0.
See all versions of reflex-browser for other recorded verdicts.
- Review the evidence and your use of reflex-browser@0.12.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.