Security audit
Security checks for vulnerabilities and agentic risk
The skill largely matches a local design-system hub, but it starts an unauthenticated development server on all network interfaces by default, which can expose hub contents to other reachable machines.
Review before installing. Prefer changing the dev server host to 127.0.0.1 unless you intentionally want LAN access, and avoid adding sensitive screenshots or proprietary briefs until the server exposure is constrained. Also consider adding a reviewed package-lock.json and using npm ci for reproducible installs.
assets/template/vite.config.ts:44Unauthenticated Development Server Exposed on All Network Interfaces
assets/template/package.json:10Unpinned Dependency Installation Without a Lockfile
The declared description describes a full-featured local design-system platform with ingestion, analysis, storage, documentation serving, and export capabilities. The actual code chunk is only a static asset defining one design system object and related tokens/metadata. While this data could support such a hub, this chunk itself does not implement the described operational behaviors. Therefore the description materially overstates the code’s actual behavior for this supplied chunk.
Referenced artifact was not completely inspected
2. Enter **Initialize** when the target has no `package.json` whose `name` is `design-hub`.
Referenced artifact was not completely inspected
5. Preserve the fixed documentation order in `DetailPage.tsx` without editing that file.
Referenced artifact was not completely inspected
| Local API middleware | `vite.config.ts` |
The instruction mandates that every user-facing explanatory field be written in Chinese whenever the user works in Chinese. This is a natural-language locale policy constraint and the file does not present it as an opt-in choice or as a clearly justified region-specific requirement.
This TypeScript file contains extensive user-facing natural-language content entirely in Chinese, including tagline, description, labels, triggers, responses, and guidelines. Under the policy, forcing a specific language without user opt-in is a natural-language policy violation unless the locale restriction is clearly documented and justified, which is not present here.
This TypeScript file contains user-facing descriptive strings in Chinese, and the same pattern continues across many descriptions and labels in the exported design system. Because the file does not offer an opt-in language choice or explain that the skill is intentionally region-specific, it creates a language/locale policy concern.
This TypeScript file contains extensive user-facing natural-language content entirely in Chinese across descriptions, labels, guidelines, and interaction text. Under the policy rule, forcing a specific language without user opt-in is a locale/language policy violation, and there is no indication in the file that users can select another language or that the constraint is region-specific.
This TSX file contains multiple hard-coded Chinese UI strings such as "体验版", "问题反馈", "分析完成，关键结果已整理为可审阅的技术报告。", "核心指标概览", "此为预览，点击查看详情。", and section labels like "待办" and "技能与 MCP". Because the file does not provide a language selection mechanism or indicate that the component is intentionally region-specific, it violates the natural-language policy against forcing a specific language without user opt-in.
The tokenUsage function returns Chinese strings for many default UI descriptions, and the component also includes additional Chinese-language notes elsewhere in the file. This appears to impose a specific language on users without offering a choice or documenting that the skill is intentionally region-specific, which matches the locale-policy violation criteria.
Several module notes and labels in these lines are presented only in Chinese, making the interface language fixed rather than user-selectable. Because the file does not indicate an explicit opt-in or justified region-specific constraint, this is a natural-language locale policy concern.
The short description is written in Chinese while the default prompt is written in English, and the file does not indicate that language is selectable by the user or that the skill is intentionally region-specific. This can create a language/locale policy issue because the skill implicitly imposes inconsistent language behavior without opt-in or justification.
The HTML root sets lang="zh-CN", which imposes a specific language/locale in the user-facing document. Under the policy, locale-specific behavior should either offer user choice or be clearly justified as region-specific, neither of which is present in this file.
Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.
"preview": "vite preview"
},
"dependencies": {
"@vitejs/plugin-react": "^6.0.1",
"vite": "^8.0.12",
"typescript": "~6.0.2",
"react": "^19.2.0",
Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.
},
"dependencies": {
"@vitejs/plugin-react": "^6.0.1",
"vite": "^8.0.12",
"typescript": "~6.0.2",
"react": "^19.2.0",
"react-dom": "^19.2.0",
Dependency has known vulnerabilities (CVEs). Using packages with unpatched security flaws exposes the environment to known exploits.
Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.
"@vitejs/plugin-react": "^6.0.1",
"vite": "^8.0.12",
"typescript": "~6.0.2",
"react": "^19.2.0",
"react-dom": "^19.2.0",
"react-router-dom": "^7.0.0",
"lucide-react": "^0.468.0"
Dependency has known vulnerabilities (CVEs). Using packages with unpatched security flaws exposes the environment to known exploits.
Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.
"vite": "^8.0.12",
"typescript": "~6.0.2",
"react": "^19.2.0",
"react-dom": "^19.2.0",
"react-router-dom": "^7.0.0",
"lucide-react": "^0.468.0"
},
Dependency has known vulnerabilities (CVEs). Using packages with unpatched security flaws exposes the environment to known exploits.
Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.
"typescript": "~6.0.2",
"react": "^19.2.0",
"react-dom": "^19.2.0",
"react-router-dom": "^7.0.0",
"lucide-react": "^0.468.0"
},
"devDependencies": {
Dependency has known vulnerabilities (CVEs). Using packages with unpatched security flaws exposes the environment to known exploits.
Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.
"react": "^19.2.0",
"react-dom": "^19.2.0",
"react-router-dom": "^7.0.0",
"lucide-react": "^0.468.0"
},
"devDependencies": {
"@types/node": "^24.0.0",
Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.
"lucide-react": "^0.468.0"
},
"devDependencies": {
"@types/node": "^24.0.0",
"@types/react": "^19.0.0",
"@types/react-dom": "^19.0.0"
}
Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.
},
"devDependencies": {
"@types/node": "^24.0.0",
"@types/react": "^19.0.0",
"@types/react-dom": "^19.0.0"
}
}
No suspicious patterns detected.