T08 · Insecure Dependencies
- Location
SKILL.md:5- Finding
Unpinned Executable Installed from a Third-Party Homebrew Tap
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This camera-capture skill is coherent, but it relies on an unpinned third-party executable and gives weak guidance around camera passwords and retained media.
Review this before installing. Use a dedicated low-privilege camera account, avoid putting real camera passwords in reusable command history or shared transcripts, protect any camsnap config file with restrictive permissions, and save snapshots or clips only to controlled locations. The Homebrew dependency comes from a third-party tap and is not pinned by this skill, so installation trust depends on that upstream package source.
SKILL.md:5Unpinned Executable Installed from a Third-Party Homebrew Tap
SKILL.md:13Camera Password Passed in Plaintext Command-Line Arguments
The skill instructs users to add cameras with --user and --pass and notes a persistent config file path, but it does not warn that camera credentials will be stored and reused from disk. This can expose sensitive surveillance access if the config file is left with weak permissions, synced, backed up insecurely, or inspected by other local users or tools.
The examples for snap and clip write image and video files to user-specified paths, but the skill does not warn that captured media is persisted to disk. This can lead to unintended retention of sensitive camera footage, especially on shared machines, synced folders, or automated agent workflows that may later expose those files.