@ricsam/r5d-browser@0.0.194-prod.1790978804883.gcdb353d09d8f56502907c31e4b50779055775603
`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 scanner's execution and evaluation findings correspond to local Chrome launching and requested page scripting. Source inspection found package-aligned authentication and browser operations, with no concrete malicious chain.
Decision evidence
public snapshot- package.json has no install lifecycle hooks or runtime self-dependency.
- The launcher starts a validated local Chrome executable; no remote executable download was found.
- Dynamic JavaScript evaluation implements the requested run_js action inside a browser page.
- Browser connection startup is activated by the start command or explicit private configuration.
- Relay requests use r5d client authentication and the configured HTTPS service origin, with redirects rejected.
- The launcher rejects Chrome's everyday profile and uses separate browser state.
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.194-prod.1790978804883.gcdb353d09d8f56502907c31e4b50779055775603.
See all versions of @ricsam/r5d-browser for other recorded verdicts.
- Review the evidence and your use of @ricsam/r5d-browser@0.0.194-prod.1790978804883.gcdb353d09d8f56502907c31e4b50779055775603 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.