Security audit
Security checks for vulnerabilities and agentic risk
This skill is a disclosed Kuaishou public-data collection tool that uses an API token, sends requested queries or URLs to its service, and saves fetched results locally.
Install only if you are comfortable sending Kuaishou keywords or URLs and your GUAIKEI_API_TOKEN to guaikei.com. Treat saved logs as retained copies of scraped public data and delete or protect them if they include sensitive research, creator identifiers, or business analysis.
The package description and keywords present the skill as a read-only data analysis tool, but the exposed scripts include active posting and commenting functionality. This mismatch can mislead users and downstream systems about the skill's capabilities, increasing the risk of unintended content publication or platform actions when the package is installed or invoked.
This markdown file presents the skill changelog entirely in Chinese, and also names the skill in Chinese, without any note that the skill is region-specific or that users may choose another language. Under the policy, forcing a specific language without user opt-in can be a natural-language policy violation.
This documentation describes collecting KuaiShou search results, creator posts, and comment data, including third-party and user-generated content, but provides no warning about privacy obligations, platform Terms of Service, consent, retention, or lawful use. In a scraping/data-collection skill, omission of these constraints increases the likelihood of misuse, over-collection, and non-compliant handling of personal data.
No manifest is available, so there is no declared purpose or permissions baseline that would justify handling credentials. This script explicitly retrieves a token from process.env and uses it to call backend comment APIs, which is a privileged capability beyond a simple local CLI transformation or parsing task.
With no manifest available, the skill has no stated purpose that would justify creating and polling remote comment-retrieval tasks. The code goes beyond local argument handling by invoking external API operations through comment.createCommentTask and comment.getCommentTask using an authentication token.
The script writes comment results to disk without a user-facing warning or explicit consent in the normal success path. This is dangerous because users may assume the tool is transient CLI output only, while it actually creates a persistent local copy of potentially sensitive third-party content.
The CLI sends a user-supplied profile URL to a remote API and later persists both the normalized URL and fetched results to a local log file, but there is no explicit notice, consent, or opt-in for network transmission or local retention. In a data-collection skill, this creates a privacy and operational security risk because sensitive profile identifiers and scraped content may be exposed to other local users, backups, or log processors without the operator realizing it.
The script persists full search output to a local file using a filename derived in part from user-controlled input (keyword) and does so without explicit user consent or a clear opt-in flag. Even if the content is not inherently secret, search queries and returned results can contain sensitive or proprietary data, and silently writing them to disk increases exposure through local disclosure, log retention, or accidental sharing.
All user-visible error messages in this file are hard-coded in Chinese, with no indication that the user can choose another language or that the skill is intentionally restricted to a Chinese-speaking context. This is a language/locale policy concern because the file imposes a specific language in natural-language responses without opt-in or justification.
This code sends request parameters/body data to a remote host and includes a TOKEN header, but there is no confirmation prompt, logging, comment, or docstring warning that user or system data may be transmitted externally. For code files, outbound network transmission and credential use should have some visible disclosure unless already clearly documented elsewhere, which is not present in this file.
This code contains user-facing warning and info strings only in Chinese, which can force a specific language experience on users without opt-in. The stated policy flags language or locale constraints unless the skill offers a choice or clearly documents a justified region-specific limitation.
The package description is written entirely in Chinese, which imposes a specific language choice in user-facing metadata without offering any alternative or opt-in. This matches the locale/language policy concern for natural-language content in configuration files.
The entire natural-language documentation is presented only in Chinese and includes Chinese-only support/contact instructions, with no indication that users may choose another language. Under the stated policy, forcing a specific language without opt-in can be a locale-policy concern unless the regional restriction is explicitly justified.
The README states that all task results are automatically saved to the local logs/ directory, but it does not clearly warn users that scraped content, URLs, keywords, and potentially sensitive business intelligence may persist on disk. This creates a privacy and operational security risk because users may unknowingly retain data longer than intended or expose it through backups, shared machines, or source-control mistakes.
The retry error message string is hard-coded in Chinese, which imposes a specific language on users or operators without any visible language selection or justification in this file. This is a natural-language locale policy concern because the file contains user-visible text but does not offer opt-in or indicate that the skill is intentionally China-specific.
The thrown error message is hard-coded in Chinese, creating a fixed-language experience with no visible user choice or documented locale constraint in this file. Hard-coded user-visible error text can violate language/locale policy when it forces one language by default.
This retry status message is hard-coded in Chinese and appears user-visible via the error-printing utility, with no indication of locale choice or scope limitation. That creates a language policy issue because the file enforces one locale rather than offering opt-in or documenting a justified restriction.
This code performs HTTP POST/GET operations using a token and user-provided search parameters, which may transmit user or system data to external services. While retry errors are logged, there is no confirmation prompt, user-facing notice, or explanatory comment/docstring in this file describing that these requests send data over the network.
The script silently persists retrieved comment data to a local JSON file after printing results, which creates an unnecessary local data retention surface. If comments contain personal or sensitive data, this can expose information to other local users, backup systems, or later unintended processing, especially because the write is not clearly disclosed before execution.
The script reads GUAIKEI_API_TOKEN from the environment to authenticate API requests, but this file does not include any comment, help text, or other user-facing notice explaining that a credential will be consumed. For this rule, sensitive environment variable access should have some form of disclosure unless already clearly documented.
This JavaScript file contains natural-language comments, error messages, and help text exclusively in Chinese, including the module description, thrown errors, and CLI help output. The policy scope for all file types includes language/locale violations when a specific language is forced without user opt-in, and this file provides no alternative locale or documented justification.
The code emits user-facing error messages in Chinese only, such as the filename and content validation errors. This imposes a specific language on users without any opt-in or documented locale justification, which matches the language/locale policy concern.
The file explicitly references the GUAIKEI_API_TOKEN credential in error handling and uses a token value in request headers, but it does not include any user-facing notice or explanatory comment about credential usage. Accessing or transmitting credentials is in scope for missing-warning checks on code files when no disclosure is present.
The thrown error string 重试${maxAttempts}次后失败 forces a specific language in a user-visible message. This is a natural-language locale policy concern because the file provides no indication that Chinese output is optional, user-selected, or required by a documented regional context.
The call to new Date().toLocaleString() emits localized timestamps based on the runtime environment, while the surrounding user-facing text is hardcoded in Chinese. This creates a locale-specific user experience without offering an explicit language or locale choice, which can violate natural-language policy expectations when locale behavior should be user-selectable or documented.
Detected: suspicious.exposed_secret_literal
