T08 · Insecure Dependencies
- Location
SKILL.md:84- Finding
Mutable Third-Party Packages Are Downloaded and Executed Without Version Pinning
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is coherent and purpose-aligned, but its setup instructions include mutable package execution and plaintext admin-password command examples that users should review carefully before following.
Install only if you are comfortable reviewing and controlling the deployment steps. Pin npm/npx package versions where possible, avoid putting real admin passwords on the command line, run setup in a minimally privileged environment, and give MCP write keys only to agents you trust to modify production funnel content and checkout flows.
SKILL.md:84Mutable Third-Party Packages Are Downloaded and Executed Without Version Pinning
SKILL.md:84Administrative Password Is Passed as a Command-Line Argument
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
npm create autonnel@latest my-funnel
cd my-funnel
cp .env.example .env # set DATABASE_URL and ADMIN_DOMAIN
pnpm install # pnpm 10+; the repo pins overrides npm would ignore
npm run db:push
npm run dev # or: npm run build && npm run start
The invocation guidance says to use the skill when asked to "build, deploy or host a sales funnel or landing page," which is a wide set of common requests without clear boundaries on when this skill should be chosen versus adjacent skills. Although examples are given, the trigger scope is not tightly constrained and lacks explicit exclusion conditions beyond a brief mention of two related skills.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
Docker image references without a specific tag (:latest is implicit) or digest (@sha256:...) can be silently replaced by a malicious image.
L184 states that a LANDING page can belong to only one funnel and that reuse is rejected, but later L238 says the same page may be referenced by several funnels and there is no 'belongs to one funnel only' rule. This is an active contradiction in the skill's operational guidance and can mislead an agent about valid write behavior.
No suspicious patterns detected.