@ricsam/r5d-browser@0.0.189-prod.1790463964002.gbcfce585c96c8eb0c668f572ed7d664c7e7d8a4e
`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-aiThe package is a user-started Chrome client with no install lifecycle, and its token is sent only to the configured r5d HTTPS origin. Local Chrome spawn and in-page run_js match that browser-control purpose.
Decision evidence
public snapshot- package.json exposes the r5d-browser CLI bin and has no preinstall, install, or postinstall scripts.
- Chrome is started with spawn only after the executable path is validated, and only when the launcher runs.
- Page JavaScript runs only for an explicit browser run_js action inside the controlled page.
- Account requests use a caller-selected HTTPS origin, defaulting to https://r5d.dev, with the r5d credential.
- Remote browser control, loopback port forwards, and run_js are powerful, but they start only after the user runs the CLI and they talk to the same product origin.
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.189-prod.1790463964002.gbcfce585c96c8eb0c668f572ed7d664c7e7d8a4e.
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.1790463964002.gbcfce585c96c8eb0c668f572ed7d664c7e7d8a4e 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.