@ricsam/r5d-browser@0.0.194-prod.1791584810255.g6e25f5ef348b4a81308780c9b5404e5bb4e23d64
`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 25d ago · by lpm-firewall-aiThe flagged process execution launches Chrome, while dynamic JavaScript runs within the browser-action functionality. The inspected source shows an explicit CLI start action and token delivery to the configured HTTPS service; it does not establish an independent attack.
Decision evidence
public snapshot- The package entrypoint is the browser CLI.
- Starting the CLI is an explicit user action.
- Chrome is launched from the selected executable path.
- Browser JavaScript is dynamically invoked as part of browser actions.
- The client sends its token to the configured HTTPS service origin; the default is r5d.dev.
- No concrete malicious behavior was identified in the inspected source.
- The flagged process launch starts Chrome, and the dynamic JavaScript execution supports the browser-control function.
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.1791584810255.g6e25f5ef348b4a81308780c9b5404e5bb4e23d64.
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.1791584810255.g6e25f5ef348b4a81308780c9b5404e5bb4e23d64 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.