Security audit
Security checks for vulnerabilities and agentic risk
This skill is a disclosed Kuaishou public-data fetching tool that uses a required API token and saves results locally, with no evidence of hidden execution, privilege escalation, or destructive behavior.
Install only if you are comfortable sending Kuaishou search terms, profile/video URLs, and your GUAIKEI_API_TOKEN to the guaikei.com API. Treat the generated logs as retained research data and delete or protect them if the queries, targets, or returned comments are sensitive.
The manifest description is primarily written in Chinese and presents the skill's invocation context and behavior in that locale without any opt-in or user language selection. Under the policy rule, a language/locale constraint should either offer user choice or be clearly justified as region-specific; this line does neither.
The README says all task results are automatically saved to the logs directory, but it does not clearly warn that scraped public data, URLs, keywords, and analysis outputs may persist on disk. This creates a confidentiality and privacy risk because operators may unknowingly retain sensitive research targets, campaign data, or regulated content locally where other users, backup systems, or malware could access it.
This code persists the full command output, including the requested URL and retrieved comments, to a file via log.taskWrite. While the script logs progress to the console, there is no clear user-facing disclosure in this file that execution will create a local artifact containing potentially sensitive data.
Because no manifest is available, the skill's intended scope is unknown. This file's observable behavior includes reading a secret from process.env and using it to call backend APIs, which is a privileged capability not justified by any stated purpose in the available documentation.
The CLI persistently writes fetched results to a local JSON file without obtaining explicit user consent or clearly warning that data will be stored on disk. If the returned post data contains personal, sensitive, or regulated information, this can create unintended local data exposure through shared machines, backups, logs, or permissive filesystem access.
The CLI persists the full search output, including the user's keyword and returned results, to a local JSON file without any explicit consent, warning, retention control, or sensitivity filtering. This creates a privacy and data-exposure risk because query history and result data may remain on disk, be readable by other local users/processes, or be unintentionally collected by backups, logs, or artifact uploads.
This code's user-facing comments and error/help strings are consistently presented only in Chinese, starting with the module description. Under the policy rule, forcing a specific language without user opt-in is a natural-language locale violation unless the constraint is explicitly documented and justified.
The parser throws Chinese-language errors and generates Chinese help text such as parameter validation messages and usage output. Because the file provides no opt-in or alternative locale handling, it enforces a specific language policy across all users of the utility.
Multiple error strings in this file are presented only in Chinese, including operational and credential-related messages. For all file types, hard-coding a specific language without user opt-in or documented locale justification is a natural-language policy violation.
The code requires a token and places it into the outbound HTTP header, and the error path explicitly references the GUAIKEI_API_TOKEN credential. There is no accompanying warning, comment, or docstring explaining that a credential is being consumed and transmitted, which matches the missing-warning criterion for sensitive credentials in code files.
This utility sends request parameters, a skill identifier, and an authentication token over HTTPS via both GET query strings and POST headers, but the file contains no confirmation prompt, logging, comment, or docstring disclosing that user or system data may be transmitted externally. For code files, outbound network transmission is in scope when there is no visible warning and the disclosure is not evident in the file itself.
This JavaScript file contains multiple user-facing error strings in Chinese, such as the validation messages at L05, L10, L14, and L18. Because the file forces a specific language for user-visible output with no opt-in or locale selection mechanism, it matches the policy's language/locale violation criteria.
The description and keywords are entirely in Chinese, which can function as a language-specific instruction or presentation choice in user-facing skill metadata. The file does not indicate that this locale restriction is optional, user-selectable, or justified as a region-specific tool.
The title and changelog content are presented in Chinese, and the file does not indicate that users may choose another language or that the skill is intentionally limited to a Chinese-language audience. Under the natural-language policy rule, forcing a specific language without opt-in can be a policy violation.
This markdown file uses Chinese throughout for headings, parameter descriptions, and examples, but does not indicate that the skill is China-specific or provide an opt-in/alternative language. Under the policy rule for natural-language violations, forcing a specific language without user choice can be a locale-policy issue.
The retry/error message string is hardcoded in Chinese, which indicates a fixed language choice in user-visible output. The file provides no option for locale selection or indication that this is a justified region-specific constraint.
The thrown error message is written only in Chinese, which can violate language/locale policy when no user choice or explicit regional justification is provided. This is a natural-language policy issue rather than a code-security flaw.
The error string is hard-coded in Chinese, which imposes a specific language in user-visible output. The file does not offer any language selection or indicate that the skill is intentionally region- or locale-specific.
This thrown error message is written only in Chinese and appears to be user-visible or operator-visible output. Under the language/locale policy, forcing a single language without opt-in is a natural-language policy concern.
The retry log message is user-facing operational text and is fixed to Chinese. There is no evidence in this file of a user language choice or a documented reason for restricting output to a single locale.
The skill's descriptions and runtime messages are presented in Chinese throughout the file, and there is no indication that users can choose another language or opt in to this locale. Under the stated policy, forcing a specific language without user choice is a natural-language policy issue.
This code emits user-visible error text in Chinese (e.g. at L07 and L11), and also continues that pattern in success/error messages later in the file. For a general-purpose utility file, forcing a specific language without opt-in can violate language/locale policy requirements.
The thrown error string at L21 is written only in Chinese (重试${maxAttempts}次后失败), which imposes a specific language on users regardless of their locale or preferences. This is a natural-language policy concern because the file provides no option to select or localize the message.
This utility prints a banner and comment text in Chinese only, including the visible user-facing banner string. The file provides no indication that users can choose their preferred language or that the locale restriction is documented as intentional and justified.
Detected: suspicious.exposed_secret_literal
