registry / @taole/dd-playwright / 0.1.4
@taole/dd-playwright@0.1.4
⚠ 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 package source does not establish a concrete attack, and the static indicators align with browser automation and local service management. Playwright is a selected runtime dependency whose source was unavailable in this snapshot, so the review cannot resolve the behavior needed for a clean verdict.
Static reason
One or more suspicious static signals were detected.
Trigger
Using the browser or MCP entrypoints activates the Playwright dependency.
Impact
The unresolved dependency leaves runtime behavior uncertain; no specific harm was established from the inspected source.
Mechanism
The package launches Chromium and can navigate to a URL supplied by the caller using the selected browser context; Playwright’s dependency source was unavailable for inspection.
AI rationale
The inspected package source does not establish a concrete attack, and the static indicators align with browser automation and local service management. Playwright is a selected runtime dependency whose source was unavailable in this snapshot, so the review cannot resolve the behavior needed for a clean verdict.
Evidence
package.jsonsrc/browser-check.mjsbin/mcp-server.mjssrc/browser-manager.mjs
Decision evidence
public snapshotAI called this Manual Review at 76.0% confidence as Unknown with medium false-positive risk.
AI review observations
- package.json declares Playwright 1.64.1 as a runtime dependency, and browser-check.mjs imports it for Chromium setup.
- The MCP navigation tool passes its caller-supplied URL to the browser manager; saved account state is applied to the browser context.
- The inspected authentication code reads cookies scoped to Tuwan domains for the package’s account flow.
- The supplied snapshot does not include inspectable Playwright source, so its runtime behavior remains unresolved.
Evidence against
- No install lifecycle hook is declared in package.json.
- The inspected source shows no confirmed credential transfer to an unrelated recipient or other concrete attack behavior.
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 · L811import { chromium } from "playwright";
import { existsSync } from "node:fs";
import { execSync } from "node:child_process";
let cachedChromiumMeta = null;
/**
* 获取当前 Chr
Low
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 Evidencesrc/browser-check.mjs
Affected versions and remediation
This report applies to @taole/dd-playwright@0.1.4.
See all versions of @taole/dd-playwright for other recorded verdicts.
- Review the evidence and your use of @taole/dd-playwright@0.1.4 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.