T08 · Insecure Dependencies
- Location
scripts/lib/wait.js:1- Finding
Security-Critical Runtime Logic Is Loaded from Unpinned Modules Outside the Project Boundary
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This WeryAI video skill is disclosed as a paid API integration, but its real runtime logic is delegated to unaudited files outside the package, so installation deserves manual review.
Install only if you trust the surrounding runtime that provides the external core/weryai-core and core/weryai-video modules. Treat WERYAI_API_KEY as a paid credential, avoid endpoint overrides unless you fully control the host, and prefer a package that vendors or pins the runtime implementation before using it for production or sensitive media.
scripts/lib/wait.js:1Security-Critical Runtime Logic Is Loaded from Unpinned Modules Outside the Project Boundary
scripts/lib/cli.js:31Unrestricted API Endpoint Overrides Can Redirect Credential-Bearing Requests
This code chunk does not implement text-to-video, image-to-video, storyboard-to-video, first/last-frame transitions, polling for final video output, status checks, model switching, or dry-run payload previews. Instead, it is a command-line wrapper for checking remaining WeryAI video balance. That is a materially different primary purpose and an undeclared capability relative to the description, so this is a mismatch.
The supplied code chunk does not implement any of the declared video-related functionality. Instead, it imports executeBalance from a balance module and exports it as the skill's execute function. This suggests the skill's actual purpose is to perform a balance-related operation, which is materially different from the declared purpose of text/image/storyboard-based video generation and status handling. Therefore, the description does not accurately represent the code behavior.
The declared description presents a full video-generation and transformation capability set. However, the supplied code chunk is limited to a single export statement that re-exports error utilities from a shared core module. This is materially different from the declared primary purpose and does not demonstrate the advertised behaviors. While this file could be a supporting utility within a larger skill, based on the supplied code chunk alone, the description does not accurately represent what this code actually does.
This code chunk is a thin barrel export that forwards exports from a core normalization module. Based only on the supplied code, the observable purpose is exposing shared normalization functionality, not implementing the declared WeryAI video features. Because the declared description centers on end-user video creation and related orchestration capabilities, while the actual snippet contains only a generic re-export with no visible video-specific logic, the description does not accurately represent this code chunk.
The declared description focuses on video creation and transformation workflows. However, the code chunk only exposes a command-line script whose stated help text is to list WeryAI video models and capabilities, with an optional mode filter. That is a materially different primary purpose from generating videos or managing video generation jobs. Therefore the description does not accurately represent this code chunk.
Without declared permissions the skill's intent is opaque and cannot be validated.
This code accesses a sensitive credential via process.env.WERYAI_API_KEY, but the file provides no confirmation, logging, comment, or docstring disclosing that credential material is being consumed. For code files, accessing sensitive environment variables can warrant a warning when there is no visible disclosure and the behavior is not otherwise explained here.
No suspicious patterns detected.