@ricsam/r5d-browser@0.0.189-prod.1790573615057.g96ca294c13afd8bf05d0edee140351c9be25b872
`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 concrete malicious behavior. The privileged browser actions are package-aligned and caller-invoked.
Decision evidence
public snapshot- The package entry point is the bundled browser CLI module.
- Chrome debugging connections are restricted to a loopback WebSocket endpoint with an expected DevTools path.
- The JavaScript facility requires caller-provided code and runs it in the selected browser page context.
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.1790573615057.g96ca294c13afd8bf05d0edee140351c9be25b872.
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.1790573615057.g96ca294c13afd8bf05d0edee140351c9be25b872 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.