@ricsam/r5d-browser@0.0.190-prod.1790659823295.gd12fcfe0bda24ad909c87aeceb4c37d540ffbe11
`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 hook or concrete malicious behavior. Network authentication and browser control are aligned with the package's explicit CLI function and include local endpoint and HTTPS-origin checks.
Decision evidence
public snapshot- The manifest exposes module and CLI entrypoints and contains no lifecycle-script section.
- The Chrome debugger connection rejects endpoints outside the local loopback address and expected port.
- The browser runtime operates tracked tabs and performs normal page navigation.
- The personal client requires an HTTPS origin and sends its bearer token only to routes under that selected origin.
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.190-prod.1790659823295.gd12fcfe0bda24ad909c87aeceb4c37d540ffbe11.
See all versions of @ricsam/r5d-browser for other recorded verdicts.
- Review the evidence and your use of @ricsam/r5d-browser@0.0.190-prod.1790659823295.gd12fcfe0bda24ad909c87aeceb4c37d540ffbe11 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.