registry / @taole/dd-playwright / 0.1.2
@taole/dd-playwright@0.1.2
⚠ Under reviewStandalone stdio MCP & CLI: Playwright browser automation + isolated whistle proxy + diandian account storageState injection
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe inspected source shows browser automation and service-aligned account verification, with no install hook or confirmed unrelated credential recipient. The selected Playwright dependency could not be inspected, so its runtime behavior remains unresolved.
Static reason
One or more suspicious static signals were detected.
Trigger
The MCP server is started by its caller; browser setup occurs when a browser operation needs Chromium.
Impact
The available source does not establish credential theft or another attack, but the browser runtime path cannot be fully assessed.
Mechanism
The package loads saved browser state into a Playwright context and navigates to a caller-provided URL; the dependency implementation could not be reviewed.
AI rationale
The inspected source shows browser automation and service-aligned account verification, with no install hook or confirmed unrelated credential recipient. The selected Playwright dependency could not be inspected, so its runtime behavior remains unresolved.
Evidence
package.jsonbin/mcp-server.mjssrc/browser-manager.mjssrc/browser-check.mjssrc/auth/diandian-auth.mjs
Decision evidence
public snapshotAI called this Manual Review at 76.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The package declares Playwright as a runtime dependency and uses it to launch browser automation.
- If Chromium is missing, a user-triggered browser setup runs the Playwright install command.
- The browser navigation API loads a caller-provided URL into a context that may contain saved account state; the unresolved Playwright source leaves that runtime path incomplete to review.
Evidence against
- The manifest has no install lifecycle hook.
- The inspected account verification request sends cookies to the package’s stated Diandian user-info endpoint.
- Browser setup is reached through runtime use, and the inspected source shows no confirmed credential export to an unrelated recipient.
Behavioral surface
ChildProcessEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
4 flaggedsrc/server/daemon.mjsView file
1import { spawn } from "node:child_process";
L2: import { existsSync, readFileSync, writeFileSync, unlinkSync, openSync } from "node:fs";
High
Child Process
Package source references child process execution.
src/server/daemon.mjsView on unpkg · L1src/browser-check.mjsView file
81// 调用 playwright 内置命令安装 chromium
L82: execSync("npx playwright install chromium", {
L83: stdio: silent ? "ignore" : "inherit",
High
Runtime Package Install
Package source invokes a package manager install command at runtime.
src/browser-check.mjsView on unpkg · L81package.jsonView file
17
Findings
3 High3 Medium6 Low
HighChild Processsrc/server/daemon.mjs
HighShell
HighRuntime Package Installsrc/browser-check.mjs
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowEval
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Dependency Evidencepackage.json
LowSuspicious Dependency Evidencebin/mcp-server.mjs
Affected versions and remediation
This report applies to @taole/dd-playwright@0.1.2.
See all versions of @taole/dd-playwright for other recorded verdicts.
- Review the evidence and your use of @taole/dd-playwright@0.1.2 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.