Back to skill

Security audit

Antd Vue Components

Security checks for vulnerabilities and agentic risk

Overview

This is a documentation-only Ant Design Vue component reference with no hidden execution, persistence, or credential handling found.

Install/use this as a normal documentation skill. When following its quickstart, prefer pinned package versions or a lockfile for reproducible installs, and review any real Upload action/custom-request endpoint before sending files to a server.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (1)

T08 · Insecure Dependencies

Warning
Location
references/conventions.md:225
Finding

Mutable npm Packages Are Downloaded and Executed Without Reproducible Version Pinning

Content
View full analysis
Remediation
View remediation
``` 3. Generate and commit `package-lock.json`, then recommend reproducible installation with: ```bash npm ci ``` 4. Review transitive dependencies and npm lifecycle scripts before approving dependency updates. 5. Use a trusted, explicitly configured npm registry and retain package integrity metadata from the lockfile. 6. Consider running scaffolding and installation commands in an isolated development container or other restricted environment, particularly when testing dependency updates. 7. Add an update policy requiring security review and automated dependency scanning before changing pinned versions. ]]>
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (4)

Ae1

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 35)May include surrounding context.

md
| **Feedback** | [feedback.md](references/feedback.md) | Alert · Drawer · Message · Modal · Notification · Popconfirm · Progress · Result · Skeleton · Spin · Wa

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
88% confidence
Finding

The documentation includes a locale configuration example that hardcodes zhCN for the UI locale. Because this file is general-purpose conventions documentation rather than a region-specific skill, forcing a specific language/locale in examples can conflict with organizational language/locale policy unless user choice or justification is provided.

Content

No source excerpt is available for this finding.

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
82% confidence
Finding

This markdown file includes an Upload component section that discusses real uploads via an action URL or :custom-request, but it does not warn users that selected files may be transmitted to a server. For markdown files, SQP-2 applies when descriptions omit warnings about behaviors that could affect user data or privacy.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
85% confidence
Finding

The documentation gives :locale — i18n pack (e.g. zh_CN) as the sole locale example, which can encourage a fixed-language configuration without mentioning user choice or region-specific justification. Under the policy, language or locale constraints should be optional or clearly justified rather than implicitly imposed.

Content

No source excerpt is available for this finding.