@ricsam/r5d-browser@0.0.192-prod.1790782151911.gb0e03488e305bcb4da332fd718062b0a82d2bbc3
`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 inspected execution and network primitives implement the package's browser automation function and activate through explicit CLI configuration. No concrete malicious behavior was established in the inspected source.
Decision evidence
public snapshot- package.json has no install lifecycle hooks or runtime self-dependency; its dependencies support browser automation.
- main.mjs starts the personal browser service through the explicit start command.
- chrome-launcher.mjs restricts debugging to loopback and rejects Chrome's daily-driver profile.
- browser-runtime.mjs executes supplied JavaScript inside the browser page as a requested run_js action.
- personal-main.mjs authenticates to the configured HTTPS service using an r5d credential and rejects redirects.
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.1790782151911.gb0e03488e305bcb4da332fd718062b0a82d2bbc3.
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.1790782151911.gb0e03488e305bcb4da332fd718062b0a82d2bbc3 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.