@ricsam/r5d-browser@0.0.194-prod.1791273966632.gce0c4adaebaeb6724d09f77a55286a80378775ed
`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 flagged execution and evaluation primitives are consistent with the inspected browser automation implementation. Static inspection found no concrete malicious chain; the download-and-execute hint is unsupported by the launcher source.
Decision evidence
public snapshot- package.json has no lifecycle hooks or runtime self-dependency; its dependencies support browser automation.
- The Chrome launcher resolves an installed executable and starts it with browser arguments; no remote executable download was found.
- Dynamic evaluation implements the requested run_js browser action inside page.evaluate.
- The CLI activates the personal browser through the start command and parsed options.
- Authentication uses caller configuration or r5d credentials for the configured HTTPS API origin, defaults to https://r5d.dev, 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.194-prod.1791273966632.gce0c4adaebaeb6724d09f77a55286a80378775ed.
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.1791273966632.gce0c4adaebaeb6724d09f77a55286a80378775ed 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.