@ricsam/r5d-browser@0.0.190-prod.1790608865887.gb65bd463ec0dd3b76c7e218ea1e8f7f7ade9bcd7
`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 no install hook, self-dependent lifecycle chain, or concrete malicious behavior. The exposed browser-control capabilities are package-aligned and locally constrained.
Decision evidence
public snapshot- The package metadata defines library and CLI entrypoints and contains no lifecycle script or self-dependency.
- The Chrome launcher rejects debugger WebSocket endpoints unless they use the expected loopback host, port, and DevTools path.
- Browser JavaScript execution is an explicit run_js action and requires string code.
- Artifact writes use exclusive creation in the package download location.
Source & flagged code
5 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.190-prod.1790608865887.gb65bd463ec0dd3b76c7e218ea1e8f7f7ade9bcd7.
See all versions of @ricsam/r5d-browser for other recorded verdicts.
- Review the evidence and your use of @ricsam/r5d-browser@0.0.190-prod.1790608865887.gb65bd463ec0dd3b76c7e218ea1e8f7f7ade9bcd7 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.