@ricsam/r5d-browser@0.0.195-prod.1793121269113.g251ff68056488b47cf3a80b04bb0973e4470107f
⚠ Under review`r5d-browser start` updates the client automatically. It checks the authenticated environment's selected release once a minute and stages verified packages privately using npm. After the current action finishes, it reconnects a new CLI process to the same
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe inspected source supports ordinary browser-client behavior and does not establish a malicious action. Because the selected ws dependency is used in the active launcher path and its source could not be inspected, the evidence is insufficient to mark the package clean.
Decision evidence
public snapshot- The manifest declares ws as a dependency, and the active Chrome launcher imports it.
- The launcher creates a WebSocket for a browser endpoint; the dependency’s source is missing from the inspected snapshot.
- The start command invokes the personal browser startup path.
- The browser resolves its credential and server from supplied flags, configuration, or environment, requires HTTPS, and sends relay requests to that resolved origin.
- The inspected source did not establish an attack or an unrelated credential recipient; the review remains incomplete because the imported WebSocket dependency could not be inspected.
Source & flagged code
5 flaggedPackage contains a possible secret pattern.
dist/mjs/browser-secret-fill.mjsView on unpkg · L118Findings
Affected versions and remediation
This report applies to @ricsam/r5d-browser@0.0.195-prod.1793121269113.g251ff68056488b47cf3a80b04bb0973e4470107f.
See all versions of @ricsam/r5d-browser for other recorded verdicts.
- Review the evidence and your use of @ricsam/r5d-browser@0.0.195-prod.1793121269113.g251ff68056488b47cf3a80b04bb0973e4470107f 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.