registry / @ricsam/r5d-browser / 0.0.194-prod.1791827233012.gbd5cb3762aaa49810f093a34464b207c7d3bee96
@ricsam/r5d-browser@0.0.194-prod.1791827233012.gbd5cb3762aaa49810f093a34464b207c7d3bee96
⚠ Under review`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
Static Scan Results
scanned 23d ago · by rust-scannerStatic analysis completed at 0.0% confidence. No malicious behavior was detected; 12 low-signal pattern(s) were surfaced and cleared.
Static reason
Automated AI review exhausted its retry budget. This package remains unresolved and must not warn or block users.
Decision evidence
public snapshotBehavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkWebSocket
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
5 flaggeddist/mjs/chrome-launcher.mjsView file
1import { spawn } from "node:child_process";
L2: import fs from "node:fs";
L3: import http from "node:http";
L4: import net from "node:net";
...
L9: import WebSocket from "ws";
L10: import { readChromeSession, writePrivateJson } from "./chrome-session-state.mjs";
L11: const DEFAULT_STARTUP_TIMEOUT_MS = 15e3;
...
L21: }
L22: function defaultChromeProfilePath(homeDirectory = os.homedir()) {
L23: return path.join(homeDirectory, ".r5d", "browser", "chrome-profile");
...
L45: function resolveChromeExecutable(options = {}) {
L46: const env = options.env ?? process.env;
Critical
Download Execute
Source downloads or fetches remote code and executes it.
dist/mjs/chrome-launcher.mjsView on unpkg · L11Trigger-reachable chain: manifest.main -> dist/mjs/main.mjs -> dist/mjs/personal-main.mjs -> dist/mjs/chrome-launcher.mjs
L1: import { spawn } from "node:child_process";
L2: import fs from "node:fs";
L3: import http from "node:http";
L4: import net from "node:net";
...
L9: import WebSocket from "ws";
L10: import { readChromeSession, writePrivateJson } from "./chrome-session-state.mjs";
L11: const DEFAULT_STARTUP_TIMEOUT_MS = 15e3;
...
L21: }
L22: function defaultChromeProfilePath(homeDirectory = os.homedir()) {
L23: return path.join(homeDirectory, ".r5d", "browser", "chrome-profile");
...
L45: function resolveChromeExecutable(options = {}) {
L46: const env = options.env ?? process.env;
Findings
2 Critical3 High3 Medium4 Low
CriticalDownload Executedist/mjs/chrome-launcher.mjs
CriticalTrigger Reachable Dangerous Capabilitydist/mjs/chrome-launcher.mjs
HighChild Processdist/mjs/chrome-launcher.mjs
HighEvaldist/mjs/browser-runtime.mjs
HighSemantic Analysis Limiteddist/mjs/browser-runtime.mjs#virtual:string-array:round1
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @ricsam/r5d-browser@0.0.194-prod.1791827233012.gbd5cb3762aaa49810f093a34464b207c7d3bee96.
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.1791827233012.gbd5cb3762aaa49810f093a34464b207c7d3bee96 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.