@ricsam/r5d-browser@0.0.189-prod.1790099582064.g0c0e53385eca73d6552fbc0c039b446f3d809d80
`r5d-browser start --auto-update` enables automatic client updates for this environment and state directory. The setting persists; `--no-auto-update` disables it. The client checks the authenticated environment's selected release once a minute and stages
AI Security Review
scanned 1mo ago · by lpm-firewall-aiStatic inspection found a browser automation CLI with expected process and page-script capabilities, but no lifecycle hook or concrete malicious behavior. Local DevTools endpoint validation limits the observed connection surface.
Decision evidence
public snapshot- The manifest exposes a module and CLI entrypoint and contains no lifecycle script.
- The Chrome launcher rejects DevTools WebSocket URLs unless they are loopback endpoints on the allocated port.
- Chrome is launched only through the launcher with a resolved executable and constructed argument array.
- Page JavaScript execution is an explicit run_js browser operation and is evaluated in the selected page context.
Source & flagged code
6 flaggedSource downloads or fetches remote code and executes it.
dist/mjs/chrome-launcher.mjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @ricsam/r5d-browser@0.0.189-prod.1790099582064.g0c0e53385eca73d6552fbc0c039b446f3d809d80.
See all versions of @ricsam/r5d-browser for other recorded verdicts.
- Review the evidence and your use of @ricsam/r5d-browser@0.0.189-prod.1790099582064.g0c0e53385eca73d6552fbc0c039b446f3d809d80 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.