@ricsam/r5d-browser@0.0.192-prod.1790779846324.g7c9e4b58272e7d64a9db5713ea43cdf02f51011a
`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-aiSecurity-sensitive behavior is consistent with the explicitly activated browser automation client. Static inspection found no install-hook abuse, concealed payload execution, foreign agent configuration mutation, or concrete credential theft.
Decision evidence
public snapshot- package.json declares a browser CLI and ordinary dependencies, with no lifecycle hooks or runtime self-dependency.
- The Chrome launcher spawns the selected Chrome executable with browser launch arguments.
- The run_js operation evaluates supplied code inside a browser page.
- The main entrypoint requires the start command or an explicit private keeper configuration to activate browser services.
- Personal browser requests authenticate to the configured r5d API origin and reject redirects.
- The isolated Chromium runtime enforces an approved origin allowlist.
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.192-prod.1790779846324.g7c9e4b58272e7d64a9db5713ea43cdf02f51011a.
See all versions of @ricsam/r5d-browser for other recorded verdicts.
- Review the evidence and your use of @ricsam/r5d-browser@0.0.192-prod.1790779846324.g7c9e4b58272e7d64a9db5713ea43cdf02f51011a 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.