@ricsam/r5d-browser@0.0.189-prod.1790390627202.g1023d9102362d95006cf88932e9628eea98bed5f
`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 configurable destination is not bound to the credential's intended service, creating a concrete conditional credential-exposure risk. The inspected package has no lifecycle hook, so blocking is not supported.
Decision evidence
public snapshot- The manifest exposes a JavaScript CLI entry point.
- The start command initializes the personal browser connection.
- The connection accepts a configurable HTTPS origin and obtains a token from options, configuration, or environment variables.
- Requests send that token as a bearer credential to the configured origin without a destination allowlist.
- The Chrome launcher refuses the user's daily-driver Chrome profile.
- The browser runtime can execute supplied JavaScript in the controlled page.
- No npm lifecycle hook is declared in the inspected manifest.
- The credential transfer occurs only when the user invokes the start command and configures a connection.
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.1790390627202.g1023d9102362d95006cf88932e9628eea98bed5f.
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.1790390627202.g1023d9102362d95006cf88932e9628eea98bed5f 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.