dsh-volcengine-provider@0.2.11
⚠ Under review火山方舟 Agent Plan 与 Coding Plan:OAuth 登录、账号、模型与额度管理。
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe readable source indicates a bounded, user-triggered OAuth URL handoff and no install-time behavior. The Windows executable that implements the PATH interception is opaque to the available inspection, so its behavior cannot be established from the package contents.
Decision evidence
public snapshot- The manifest lists build, test, and check scripts, with no install lifecycle hook.
- The Windows login flow adds the package's rundll32.exe directory to the ArkCli child process PATH during an explicit startLogin operation.
- The bundled Windows executable is a 5,632-byte PE artifact, but the available offline inspection could not analyze its format.
- The documentation and JavaScript describe the intended helper as forwarding the official login URL to a loopback listener; the executable's actual behavior could not be verified.
- The readable code requires a verified Windows ArkCli version and routes the bridge through a random-token authenticated listener bound to 127.0.0.1.
- The documented login flow does not replace system files or registry settings, and the helper is invoked only as part of user-started OAuth login.
Source & flagged code
5 flaggedPackage ships native binary artifacts.
lib/browser-bridge/win32/rundll32.exeView on unpkgA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
cordis.patch.ymlView on unpkgFindings
Affected versions and remediation
This report applies to dsh-volcengine-provider@0.2.11.
See all versions of dsh-volcengine-provider for other recorded verdicts.
- Review the evidence and your use of dsh-volcengine-provider@0.2.11 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.