Security audit
Security checks for vulnerabilities and agentic risk
This skill does what it claims: it fetches public Xiaohongshu data through a third-party API, but users should understand that tokens, URLs, and full results are sent or stored as part of normal operation.
Install only if you are comfortable sending Xiaohongshu keywords, profile/note URLs, and your Guaikei API token to the Guaikei service. Treat generated logs as sensitive because they can contain research targets, collected comments, profile/note URLs, and xsec_token-bearing links; delete or protect logs on shared systems.
src/utils/request.js:71API Credential Exposure Through URL Query Parameters
src/utils/log.js:5Automatic Plaintext Storage of Collected Data and Capability-Bearing URLs
The supplied code does not implement the declared Xiaohongshu data collection assistant behavior. Instead, it is a reusable command-line argument parser utility. It only parses CLI flags, positional arguments, defaults, required parameters, and help text. While such a utility could support a larger scraping tool, this code chunk itself does not access Xiaohongshu, perform network requests, collect public data, retrieve notes/comments, or monitor posting activity. Therefore, the description does not accurately represent what this code chunk actually does.
The declared description promises a full Xiaohongshu data collection tool with multiple scraping/monitoring capabilities. However, this code chunk contains only generic utility functions for printing a banner and colored logs to stderr. Those utilities may support a larger scraper, but by themselves they do not implement or demonstrate the declared primary purpose. Therefore, for this supplied code chunk, the description does not accurately represent the actual behavior shown.
Referenced artifact was not completely inspected
- "分析这条小红书笔记评论区的主要观点和负面反馈: node src/xiaohongshu/detail-cli.js --url 'https://www.xiaohongshu.com/explore/xxx?xsec_token=yyy' --limit 100"
Referenced artifact was not completely inspected
- "分析这条小红书笔记评论区的主要观点和负面反馈: node src/xiaohongshu/detail-cli.js --url 'https://www.xiaohongshu.com/explore/xxx?xsec_token=yyy' --limit 100"
Referenced artifact was not completely inspected
- "分析这条小红书笔记评论区的主要观点和负面反馈: node src/xiaohongshu/detail-cli.js --url 'https://www.xiaohongshu.com/explore/xxx?xsec_token=yyy' --limit 100"
Referenced artifact was not completely inspected
- "看这个小红书博主最近 20 条作品都在发什么: node src/xiaohongshu/post-cli.js --url 'https://www.xiaohongshu.com/user/profile/xxx?xsec_token=yyy' --limit 20"
Referenced artifact was not completely inspected
- "看这个小红书博主最近 20 条作品都在发什么: node src/xiaohongshu/post-cli.js --url 'https://www.xiaohongshu.com/user/profile/xxx?xsec_token=yyy' --limit 20"
Referenced artifact was not completely inspected
- "看这个小红书博主最近 20 条作品都在发什么: node src/xiaohongshu/post-cli.js --url 'https://www.xiaohongshu.com/user/profile/xxx?xsec_token=yyy' --limit 20"
Without declared permissions the skill's intent is opaque and cannot be validated.
The package description and keywords are entirely in Chinese, which constitutes a natural-language locale constraint in user-facing metadata. There is no indication that the skill is region-specific by design or that users can opt into a preferred language, so this may violate language/locale policy requirements.
The skill is consistently described as a Xiaohongshu public-data collector in the manifest and throughout the README, but line L25 states '获取抖音评论详情', which refers to Douyin comments. That inline documentation contradicts the stated platform-specific intent and misrepresents what the skill is for.
The README states that all task results are automatically saved under logs/ but does not clearly warn that collected public-platform data, searched keywords, and user-supplied profile or note URLs will persist locally. In this skill's context, those artifacts can reveal research targets, monitored competitors, campaign strategy, and scraped content, increasing exposure if the host is shared, backed up broadly, or logs are later exfiltrated.
This code sends the provided API token as part of outbound HTTP requests when creating a detail task. Although the function has technical docstrings, there is no user-facing warning, confirmation, or disclosure in this file that sensitive credential data will be transmitted to an external API.
This file contains natural-language content such as module descriptions, parameter documentation, and retry/error messages exclusively in Chinese. Under the stated policy, forcing a specific language without user opt-in is a locale/language policy violation unless the constraint is explicitly justified as region-specific.
This JavaScript file contains natural-language comments and user-facing error/help text entirely in Chinese, including thrown error messages and generated CLI help output. Under the stated policy, forcing a specific language without user opt-in is a locale policy violation unless the constraint is explicitly justified, which is not present here.
The user-facing strings are entirely in Chinese and present warnings/instructions without any indication that language can be selected or changed. This creates a natural-language policy concern because the skill appears to require a specific language for critical status and recovery messaging.
This JavaScript code issues outbound HTTPS requests and may transmit query parameters and JSON payload data, but the file contains no confirmation prompt, logging, comment, or docstring disclosing that behavior. For a generic request utility, this is a safety-relevant operation that lacks any visible warning in the code itself.
Multiple thrown error messages are hard-coded in Chinese, which imposes a specific language on users without any opt-in or indication that the skill is region-specific. That is a natural-language locale policy issue under the requirement to avoid forcing a language unless the constraint is documented and justified.
The CLI silently persists the full fetched note/comment payload to a local JSON file after printing results, creating an undocumented data-at-rest side effect. Because the collected content may include sensitive research data or personal data from comments, this increases exposure on shared machines, CI runners, or agent sandboxes where users may expect transient stdout-only behavior.
The tool writes detailed task results to disk without an explicit runtime warning or user consent, which can surprise operators who expect only console output. This is especially risky in automation environments because the generated file may persist scraped comments and metadata beyond the intended session and be picked up by backups, logs, or other users.
The manifest describes a public-data collection assistant that fetches Xiaohongshu notes and returns structured data for research/analysis. In addition to printing results, this file persists the full output to disk via log.taskWrite, which is a material behavior not implied by the description's '返回结构化数据' wording.
The CLI writes the full search output to a local JSON file using a filename derived from user-controlled input, but does not clearly disclose this persistence to the user. In this skill’s context, the results can include scraped public platform data and operational metadata, so silently storing them increases the risk of unintended retention, local exposure, and downstream privacy/compliance issues on shared systems or CI environments.
The manifest description is entirely in Chinese and frames the skill for Chinese-platform workflows without stating whether other languages are supported or allowing user opt-in to a preferred language. Under the policy, language constraints should be optional or explicitly justified rather than implicitly enforced.
The user-facing example prompts are all written in Chinese and no alternative language option is provided. This suggests the skill expects a specific language/locale for activation and use, which should either be optional or clearly documented as a justified regional constraint.
The natural-language instructions and usage guidance are effectively forced into a single language/locale, with no opt-in or alternative language noted. Under the stated policy, forcing a specific language without user choice can be a locale-policy violation unless clearly justified as region-specific.