@ricsam/r5d-browser@0.0.194-prod.1791708317172.gb85ed8bc62db462e9d310736156fd8c9127729bb
`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-aiSource inspection supports a browser automation package: no lifecycle scripts are declared, and the flagged JavaScript evaluation is gated on a run_js action carrying caller-supplied code. The scanner's remote-download claim is not supported by the inspected launcher source.
Decision evidence
public snapshot- package.json points to the CLI entrypoint and declares no lifecycle scripts.
- The launcher resolves Chrome and validates a dedicated profile before starting it.
- The runtime evaluates code only when a run_js action supplies input.code; this is an explicit browser automation capability.
- The inspected launcher uses the installed Chrome executable; no remote code download or execution was found in the inspected launcher source.
- No concrete credential theft, exfiltration, persistence, or destructive behavior was established.
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.1791708317172.gb85ed8bc62db462e9d310736156fd8c9127729bb.
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.1791708317172.gb85ed8bc62db462e9d310736156fd8c9127729bb 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.