@ricsam/r5d-browser@0.0.189-prod.1790101818895.g2cde24151550775ca3fa10b950e18bbe0118592f
`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 lifecycle hook or concrete malicious behavior. Browser automation and page-script execution are explicit product capabilities with a loopback-only DevTools endpoint.
Decision evidence
public snapshot- Package metadata defines library and CLI entrypoints and contains no lifecycle install hook.
- The browser client starts only for the explicit start command.
- Chrome DevTools connections are restricted to the local loopback endpoint.
- Browser JavaScript execution requires a supplied run_js action.
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.1790101818895.g2cde24151550775ca3fa10b950e18bbe0118592f.
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.1790101818895.g2cde24151550775ca3fa10b950e18bbe0118592f 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.