@ricsam/r5d-browser@0.0.194-prod.1791642446270.g1e900da032f1be59129c162b74af22152822d823
`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 26d ago · by lpm-firewall-aiThe flagged dynamic evaluation is an explicit browser automation operation that executes code supplied to the operation, not an observed hidden package payload. Inspection found no remote code download or install lifecycle hook, and the updater is option-gated.
Decision evidence
public snapshot- package.json routes the package entrypoint to the browser CLI.
- The JavaScript escape hatch runs code supplied as an input value within the selected browser page.
- The returned result marks this execution as untrusted and says its outcome is unverified.
- Chrome is launched through a dedicated launcher; the inspected source shows no remote download or execution path.
- The CLI updater is gated by the user's auto-update option.
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.1791642446270.g1e900da032f1be59129c162b74af22152822d823.
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.1791642446270.g1e900da032f1be59129c162b74af22152822d823 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.