@ricsam/r5d-browser@0.0.194-prod.1791658759556.gf9d08624fde0f71f1ed85c9f0904d08e48add432
`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 found no lifecycle hook or remote code download in the launcher; it starts a locally resolved Chrome executable. Dynamic evaluation occurs only through the explicit run_js browser operation, consistent with the package’s browser automation purpose.
Decision evidence
public snapshot- package.json points to the browser runtime and declares no lifecycle scripts.
- The launcher resolves a local Chrome executable and dedicated profile before starting the browser.
- The run_js operation requires caller-supplied code and evaluates it in the browser page when invoked.
- The package is a browser automation tool; page JavaScript execution is an explicit feature of that runtime.
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.1791658759556.gf9d08624fde0f71f1ed85c9f0904d08e48add432.
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.1791658759556.gf9d08624fde0f71f1ed85c9f0904d08e48add432 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.