T08 · Insecure Dependencies
- Location
README.md:93- Finding
Unpinned executable dependency and mutable remote installation sources
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a straightforward Boosta API helper, with external API and API-key use that match its stated video-processing purpose.
Before installing, prefer the ClawHub package or a pinned commit/release over the unversioned npx/GitHub examples, and only submit video URLs you are allowed to share with Boosta. Store BOOSTA_API_KEY as an environment variable and avoid exposing it in logs or prompts.
README.md:93Unpinned executable dependency and mutable remote installation sources
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.
The skill requires network access and environment-secret access but does not declare an explicit tool scope such as permissions or allowed-tools. That creates an overbroad execution model where an agent may invoke capabilities beyond what a reviewer or user can easily verify, increasing the risk of unintended secret exposure or unauthorized outbound requests.
The skill instructs sending user-provided video URLs to a third-party API but does not include a clear user-facing disclosure that the URL and associated processing metadata will be shared with Boosta. This can lead to privacy and compliance issues, especially if the URL contains private, unlisted, tokenized, or otherwise sensitive content.
This code submits video_url, video_type, and optional configuration data to the remote Boosta API via _request, which performs outbound HTTP calls. While the CLI help describes the command purpose, there is no explicit warning, confirmation, or disclosure in the code about sending user-provided data to an external service.
The README promotes sending video URLs and API-key-authenticated requests to a third-party service but does not clearly warn users that their content metadata and possibly sensitive source links will be shared externally. In an automation/agent context, this can lead to unintentional disclosure of private or proprietary media inputs because users may assume processing is local or not fully appreciate the privacy implications.
The code reads an API key from an environment variable and uses it for authenticated requests, but only reports when the variable is missing. There is no user-facing disclosure that the skill requires and will use a sensitive credential for external API access.
No suspicious patterns detected.