@linjz/opencode-qqbot@0.3.3
QQ Bot for OpenCode AI - chat with AI coding assistant via QQ
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe flagged process execution is the plugin’s bot launcher, and the credential flows inspected lead to QQ’s service, the configured OpenCode service, or HTTPS QQ-owned attachment hosts. The detached startup is automatic but directly serves the package’s stated purpose; no unrelated collection or unrequested account action was found.
Decision evidence
public snapshot- The manifest describes a QQ bot for OpenCode and exports its plugin entry point.
- The plugin launches the bot only when QQ_APP_ID is configured and no instance is alive; it also checks periodically.
- The launcher runs the package bot as a detached child process and inherits the host environment.
- The QQ app ID and secret are sent to the package’s declared QQ token endpoint.
- Attachment downloads require HTTPS and a QQ-owned host suffix before any request; the QQ token is retried only for a permitted attachment URL.
- Plugin loading can start a persistent detached process without a separate command invocation.
- The child inherits environment variables, including any OpenCode password present in the host environment.
- The optional event probe writes event types and session IDs to a local file when explicitly enabled.
Source & flagged code
5 flaggedPackage source references child process execution.
dist/openqq-bot.jsView on unpkg · L3245Findings
Affected versions and remediation
This report applies to @linjz/opencode-qqbot@0.3.3.
See all versions of @linjz/opencode-qqbot for other recorded verdicts.
- Review the evidence and your use of @linjz/opencode-qqbot@0.3.3 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.