@ricsam/r5d-browser@0.0.191-prod.1790750362085.g90d9f28d6e94474fdf575d373a2aec97f4dcc577
`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 inspected executable behavior is consistent with a user-activated browser automation client, without install hooks, hidden recipients, or broad control-surface mutation. Configurable service authentication and page-scoped JavaScript execution do not establish malicious behavior.
Decision evidence
public snapshot- package.json defines a browser CLI with no install lifecycle hooks or runtime self-dependency.
- chrome-launcher.mjs launches the selected Chrome executable with argument arrays and rejects the ordinary Chrome profile.
- browser-runtime.mjs executes supplied JavaScript inside the browser page for the requested run_js operation.
- personal-main.mjs sends authenticated requests to the configured browser service with redirects rejected.
- main.mjs starts the personal browser through the explicit start command.
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.191-prod.1790750362085.g90d9f28d6e94474fdf575d373a2aec97f4dcc577.
See all versions of @ricsam/r5d-browser for other recorded verdicts.
- Review the evidence and your use of @ricsam/r5d-browser@0.0.191-prod.1790750362085.g90d9f28d6e94474fdf575d373a2aec97f4dcc577 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.