T08 · Insecure Dependencies
- Location
SKILL.md:16- Finding
Unpinned Third-Party Package Execution During Global Installation
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a local product-differentiation report generator with some overbroad eBay-specific marketing claims but no evidence of hidden data access, persistence, or destructive behavior.
Before installing, treat the eBay-specific claims as overstated and review the analyzer as a generic local product differentiation tool. For safer installation, pin the skills CLI and repository revision or install in an isolated environment instead of using the unpinned global npx command.
SKILL.md:16Unpinned Third-Party Package Execution During Global Installation
The core functionality substantially matches the general description of a product differentiation strategy tool: it analyzes competitor weaknesses, extracts pain points from negative reviews, identifies selling points, and generates actionable differentiation and positioning strategies. However, the declared purpose specifically claims eBay-specific seller feedback analysis. The supplied code contains no eBay-specific parsing, data model, terminology, API usage, marketplace handling, or seller-feedback-specific analysis. Instead, it is a generic review-based analyzer and even uses an Amazon-oriented identifier field ('asin'). Therefore, the description overstates marketplace-specific functionality, making it a meaningful description-behavior mismatch.
The installation command uses npx skills without pinning an exact version, which can cause users to execute whatever package/version is resolved at install time. That creates a supply-chain risk: if the package is updated maliciously, compromised, or changed incompatibly, anyone following the skill instructions may run unreviewed code on their system.
The CLI selects Chinese output unless the user explicitly passes no flag other than the absence of --zh, but the sample data and reporting logic indicate a built-in locale behavior controlled by the tool rather than user preference negotiation. This creates a locale policy concern because the skill contains explicit language-selection behavior that may force a specific language mode in some contexts without asking the user what language they want.