Security audit
Security checks for vulnerabilities and agentic risk
This skill appears to do what it claims: check YouTube live and upcoming broadcasts, while storing a local watchlist and using a YouTube API key.
Install only if you are comfortable providing a YouTube Data API key to the skill and having your watched channel list stored locally in watchlist.json. Review dependency updates before production use, and be aware that some live/full-status helper behavior and timezone labeling may be confusing.
Package name closely resembles a popular package, suggesting possible typosquatting. Attackers publish malicious packages with similar names to trick developers into installing them.
The tool named check_live_status is described as deprecated with instructions to use check_upcoming_broadcasts instead, but check_upcoming_broadcasts fetches upcoming broadcasts rather than live status. This is an active contradiction in the inline documentation because it directs callers from a live-status function to a non-live-status function.
The deprecated function says "Use check_upcoming_broadcasts instead," but this is not an equivalent replacement for checking live status. check_upcoming_broadcasts only queries upcoming broadcasts, while live status is implemented separately by get_live_broadcast, so the inline guidance actively misdirects callers about what the code actually does.
The helper functions and wrapper hard-code HKT as the local time context and attach it to tool results without any user choice or documented region-specific justification. This is a natural-language/locale policy issue because the skill imposes a specific locale on all outputs rather than offering opt-in or respecting user settings.
The changelog entry at L130-L137 says the documentation was updated to describe in-memory watchlist storage with no file I/O, while the current Storage Behavior section at L97-L99 states the watchlist is persisted to disk in watchlist.json. This is an active contradiction in the file's own documentation about whether the skill performs file persistence.
This code reads a credential-like environment variable (YOUTUBE_API_KEY) but provides no confirmation prompt, logging, comment about handling sensitive data, or other user-facing disclosure beyond a generic module comment. For code files, access to sensitive environment variables should include some form of warning or explanation unless clearly documented elsewhere.
This JSON manifest is a manifest file, so only SQP-1 and SQP-3 strictly do not apply here, but the tool descriptions themselves expose behavior relevant to user impact. The add_channel tool states that it adds a channel to a watchlist, yet the manifest provides no disclosure that user-supplied channel IDs, handles, or URLs will be persisted as tracked data.
The list_channels tool returns all watched channels with names and timestamps, which reveals retained watchlist contents and metadata. The manifest does not warn users that the skill maintains and can disclose this stored tracking list.
Dependency has known vulnerabilities (CVEs). Using packages with unpatched security flaws exposes the environment to known exploits.
Dependency has known vulnerabilities (CVEs). Using packages with unpatched security flaws exposes the environment to known exploits.
Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.
},
"homepage": "https://github.com/StevenHo1394/openclaw/tree/main/skills/youtube-live-broadcast-checking",
"dependencies": {
"googleapis": "^126.0.0"
},
"devDependencies": {
"nock": "^13.5.6"
Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.
"googleapis": "^126.0.0"
},
"devDependencies": {
"nock": "^13.5.6"
}
}
Detected: suspicious.exposed_secret_literal