@ricsam/r5d-browser@0.0.189-prod.1790539651296.ge5b4dba8133359b2ccbcff2e8618312c22e68ba9
`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 hooks or covert execution path. The potentially powerful browser controls are package-aligned and activated through the explicit CLI.
Decision evidence
public snapshot- The package exposes an explicit browser CLI entrypoint and declares ordinary runtime dependencies.
- The main entrypoint starts the browser service only when invoked with the start command.
- The launcher refuses to use the daily Chrome profile and requires a dedicated profile.
- Download filenames are normalized to prevent path traversal.
- The browser runtime includes an explicit JavaScript execution feature for controlled browser pages.
- The service can connect to a caller-configured HTTPS origin using a supplied authentication token.
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.1790539651296.ge5b4dba8133359b2ccbcff2e8618312c22e68ba9.
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.1790539651296.ge5b4dba8133359b2ccbcff2e8618312c22e68ba9 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.