@ricsam/r5d-browser@0.0.194-prod.1791450967742.ge619935c509ea728f45a1d0afd117276a06c01dc
`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 28d ago · by lpm-firewall-aiThe source supports a browser automation package with caller-directed JavaScript execution. Scanner hints alone do not establish a hidden download-and-execute attack, and the inspected sources show no concrete malicious behavior.
Decision evidence
public snapshot- The manifest lists the matching first-party API package and browser runtime dependencies.
- Chrome launch is part of the browser launcher and is limited to macOS.
- Dynamic code execution is exposed through an explicit browser run_js action that requires caller-provided code.
- The CLI starts the browser service through its start command.
- No lifecycle hooks are declared in package.json.
- The inspected launcher and runtime excerpts show no hidden download-and-execute path.
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.1791450967742.ge619935c509ea728f45a1d0afd117276a06c01dc.
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.1791450967742.ge619935c509ea728f45a1d0afd117276a06c01dc 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.