@ricsam/r5d-browser@0.0.191
`r5d-browser start --auto-update` enables automatic client updates for this environment and state directory. The setting persists; `--no-auto-update` disables it. The client checks the authenticated environment's selected release once a minute and stages
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe inspected source implements explicit browser-client operations and authenticated requests to its configured service. No concrete malicious behavior or automatic lifecycle execution was found.
Decision evidence
public snapshot- Package metadata has standard module and CLI entrypoints and no lifecycle hook.
- The CLI starts its client flow only for an explicit start command or private configuration invocation.
- Chrome is launched as the selected executable with controlled arguments; it refuses to attach to an already open dedicated profile.
- The run_js operation evaluates supplied code in the controlled browser page context.
- Credentials are supplied through caller options, configuration, or environment and sent only to the selected HTTPS origin.
- The package can launch and automate a browser, including executing caller-supplied page scripts.
Source & flagged code
5 flaggedSource downloads or fetches remote code and executes it.
dist/mjs/chrome-launcher.mjsView on unpkg · L1A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
Findings
Affected versions and remediation
This report applies to @ricsam/r5d-browser@0.0.191.
See all versions of @ricsam/r5d-browser for other recorded verdicts.
- Review the evidence and your use of @ricsam/r5d-browser@0.0.191 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.