@ricsam/r5d-browser@0.0.192-prod.1790855389455.g9806f32664206c21e7df4352d032f7bdfa03565b
`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-aiInspected source shows an explicitly activated browser automation client with profile isolation and authenticated service communication. No concrete malicious behavior or unresolved attack surface was established.
Decision evidence
public snapshot- package.json has no installation lifecycle hooks or runtime self-dependency.
- The Chrome launcher rejects the normal personal Chrome profile and uses a separate browser profile.
- Browser JavaScript execution handles supplied action code inside the browser page.
- The CLI activates browser service operation through explicit start arguments or private configuration.
- Relay requests authenticate to the configured service origin and reject redirects.
- The isolated browser mode enforces approved destination origins.
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.1790855389455.g9806f32664206c21e7df4352d032f7bdfa03565b.
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.1790855389455.g9806f32664206c21e7df4352d032f7bdfa03565b 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.