reflex-browser@0.12.2
Token-efficient browser automation for AI agents. Local MCP server + CLI: compressed page snapshots, batched actions, forensic failures.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiStatic inspection found a browser-automation product with local profile handling and credit-service requests, but no lifecycle hook, stealth persistence, payload execution, or concrete credential/page-data exfiltration. The scanner's exfiltration label is not supported by the inspected source.
Decision evidence
public snapshot- The package provides sensitive local browser automation and Chrome-profile handling, so its runtime paths warranted review.
- package.json declares only command-line entry points and no preinstall, install, or postinstall hook.
- The reviewed network code is for Reflex authentication, health checks, and aggregated credit metering; no source path was found sending page contents, cookies, or harvested credentials to an external host.
- Browser actions, profile copying, and daemon startup occur through the CLI or MCP runtime rather than during package installation or import.
Source & flagged code
5 flaggedA single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/reflex.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to reflex-browser@0.12.2.
See all versions of reflex-browser for other recorded verdicts.
- Review the evidence and your use of reflex-browser@0.12.2 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.