@ricsam/r5d-browser@0.0.195-prod.1793032141339.g521f3f3db9c864119c3d4b395321728b9c2754a6
⚠ 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 9d ago · by lpm-firewall-aiThe inspected source shows the saved bearer credential sent to the resolved HTTPS server origin and does not establish an unrelated recipient or concrete attack. The selected ws runtime dependency is used by the Chrome launcher, but its source was unavailable in this snapshot, so the review remains unresolved.
Decision evidence
public snapshot- package.json declares ws as a runtime dependency, and chrome-launcher.mjs uses it to connect to Chrome DevTools.
- The client resolves its server origin from flags, configuration, and environment, requires HTTPS, and sends the bearer credential to that origin.
- The inspected source does not establish a package-selected unrelated recipient or a concrete attack.
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.1793032141339.g521f3f3db9c864119c3d4b395321728b9c2754a6.
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.1793032141339.g521f3f3db9c864119c3d4b395321728b9c2754a6 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.