@ricsam/r5d-browser@0.0.194-prod.1792004703240.g9c45c744f07a303b706a8a4235a0217c47999f53
`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 21d ago · by lpm-firewall-aiThe inspected runtime behavior matches the package’s stated browser-relay function and is activated by a user starting the CLI. The source shows HTTPS requests to the resolved origin and no concrete malicious behavior.
Decision evidence
public snapshot- package.json points to the CLI entrypoint and declares no lifecycle script.
- The client resolves a configured connection, requires HTTPS, and sends bearer-authenticated requests to that same origin; its registration, polling, forwarding, and receipt calls use the shared request function.
- The CLI describes connecting a persistent Chrome profile to the r5d service, and the runtime applies actions returned by that service, including JavaScript executed in the page.
- The Chrome launcher starts the local Chrome executable, while the navigation observer watches page events.
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.1792004703240.g9c45c744f07a303b706a8a4235a0217c47999f53.
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.1792004703240.g9c45c744f07a303b706a8a4235a0217c47999f53 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.