Ae1
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md node scripts/run.mjs --sample # 先看样例
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a local cost-allocation table checker with no evidence of hidden network use, persistence, credential access, or unrelated behavior.
Install only if you are comfortable using a Chinese-language local Node.js checker for cost allocation tables. It should not be treated as accounting, audit, or tax advice, and it does not inspect ERP/MES systems directly; you provide exported table text yourself.
Referenced artifact was not completely inspected
node scripts/run.mjs --sample # 先看样例
Referenced artifact was not completely inspected
node scripts/run.mjs --sample # 先看样例
The skill’s primary display name, summary, tags, and main descriptions are all Chinese, and the operational sections of the README are also Chinese. Although there is a brief English description field, the file does not offer users a language/locale choice or indicate that Chinese-only operation is an intentional region-specific limitation.
The file’s natural-language comments and user-facing guidance are entirely in Chinese, including operational descriptions and advice strings, with no indication that the skill is region-specific or that users can opt into another language. Under the policy, forcing a specific language without user choice or clear justification is a locale-policy violation.
The user-facing description, usage text, errors, and status messages are entirely in Chinese, and the file does not indicate that language selection is optional or that the skill is intentionally limited to a Chinese-only audience for compliance or regional reasons. This creates a natural-language locale policy issue because the skill effectively enforces one language without opt-in.
The inline documentation states that non-JSON input is treated as '直接粘贴的合同全文', which contradicts the rest of the file's stated purpose of checking cost-allocation tables. The implementation passes arbitrary text to the engine, but all surrounding usage/help text consistently requires a cost allocation table with headers, so the comment describes the wrong business intent.